generated: '2026-08-09'
method: derived
source: >-
  mcp/legal-ge-public-apis-tools-list.json (live stdio tools/list) bound to
  openapi/legal-ge-public-apis-openapi.yml (OpenAPI 3.1.0, 6 operations)
summary: >-
  The MCP surface is a deliberate SUBSET of the REST surface: two matching tools over five REST
  operations. Both bindings are exact and confirmed in the server source
  (src/index.ts callAskApi -> POST /api/ask, callClassifyApi -> GET /api/ask/classify), so both
  tools inherit a real inputSchema from their backing operation. There are no MCP-only tools —
  nothing on the agent surface exists that the REST API does not expose.
surfaces:
  openapi:
    file: openapi/legal-ge-public-apis-openapi.yml
    original: openapi/_original/legal-ge-public-apis-openapi.json
    url: https://legal.ge/api/openapi.json
    gated: false
    operations: 6
  mcp:
    package: '@legalge/mcp'
    transport: stdio
    tools_list_gated: false
    file: mcp/legal-ge-public-apis-tools-list.json
  graphql: null
crosswalk:
  - tool: find_legal_specialists
    category: matching
    rest: [askMatchSpecialists]
    binding: rest
    confidence: high
    note: >-
      Verified in src/index.ts — the tool POSTs to {BASE_URL}/api/ask with {query, locale, limit}.
      The tool's default limit is 10 while the OpenAPI default is 20; both honour the 1-50 range.
      The tool default locale is 'en' while the OpenAPI default is 'ka'.
  - tool: classify_legal_intent
    category: matching
    rest: [classifyLegalIntent]
    binding: rest
    confidence: high
    note: >-
      Verified in src/index.ts — the tool GETs {BASE_URL}/api/ask/classify?q=&locale=. Tool default
      locale is 'en'; the OpenAPI parameter default is 'ka'.
mcp_only: []
rest_only:
  - operationId: askMatchSpecialistsGet
    capability: matching
    reason: >-
      Query-parameter form of POST /api/ask. The MCP server always uses the POST form, so this
      operation has no distinct tool — it is not a capability gap.
  - operationId: searchServicesAndCategories
    capability: directory
    reason: Service/category taxonomy search (GET /api/service-search) is not exposed as an MCP tool.
  - operationId: searchSpecialistsByName
    capability: directory
    reason: Specialist name lookup (GET /api/specialists/search) is not exposed as an MCP tool.
  - operationId: revealSpecialistContact
    capability: directory
    reason: >-
      Click-to-reveal contact endpoint (GET /api/specialists/{id}/contact). Deliberately absent from
      the agent surface — it is PII-bearing, opt-in, and rate-limited to 10 req/min per IP to make
      bulk harvest impractical.
coverage:
  tools_named: 2
  tools_bound: 2
  mcp_only: 0
  rest_operations_total: 6
  rest_operations_with_tool: 2
  rest_only: 4