CData · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Example Server MCP API

3 actions 3 updates phrasing extends openapi/cdata-mcp-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for CData's API. It is a proposal applied on top of the contract, not a document CData publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/mcp'].post
$.paths['/mcp/connections/{connectionId}'].post

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Example Server MCP API
  version: 1.0.0
extends: openapi/cdata-mcp-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-02'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/mcp'].post
  update:
    x-apievangelist-phrasing:
      intent: Send an MCP request across all my connections
      effect: write
      questions:
      - How do I talk to the CData Connect AI MCP server from my own model-aware client?
      - Can one MCP session reach every connection listed in my token instead of just one?
      - Is it possible to send an MCP notification without waiting for a response?
      - Which tool types can I filter out of a tools/list call on the general MCP endpoint?
      instructions:
      - text: Send the MCP method {method} to the general MCP endpoint covering all my connections.
        slots:
          method: requestBody.method
      - text: List MCP tools across all my connections, limited to tool types {tools}.
        slots:
          tools: query.tools
      - text: Call MCP method {method} with params {params} on the unscoped MCP endpoint.
        slots:
          method: requestBody.method
          params: requestBody.params
      method: generated
      generated: '2026-10-02'
- target: $.paths['/mcp/connections/{connectionId}'].post
  update:
    x-apievangelist-phrasing:
      intent: Send an MCP request scoped to one connection
      effect: write
      questions:
      - Can I restrict an MCP session to a single data connection?
      - How do I list only the MCP tools that belong to one specific connection?
      - What happens if I filter tools/list by operation names on a connection-scoped session?
      instructions:
      - text: Send MCP method {method} scoped only to connection {connectionId}.
        slots:
          method: requestBody.method
          connectionId: path.connectionId
      - text: List the MCP tools for connection {connectionId} limited to operations {ops}.
        slots:
          connectionId: path.connectionId
          ops: query.ops
      - text: Initialize an MCP session pinned to connection {connectionId}.
        slots:
          connectionId: path.connectionId
      method: generated
      generated: '2026-10-02'