Skip to main content
Glama

Describe a connected source read

playground_connected_source_schema
Read-onlyIdempotent

Get the current exact input schema and tool version for one selected account and allowlisted read operation. Returns the operation version, input schema and pagination guidance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "accountId": "<accountId>",
      "operationId": "<operationId>"
    },
    "name": "playground_connected_source_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesConnected account ID returned by connected_sources_list.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
operationIdYesRead operation ID returned by connected_sources_list; inspect its schema before supplying arguments.

Output Schema

NameRequiredDescriptionDefault
pageNo
slugYes
versionYes
accountIdYes
inputSchemaYes
operationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that the response includes the operation version and pagination guidance, which is helpful, but says nothing about failure modes (e.g. what happens with a non-allowlisted operationId) or how version drift should be handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action and scope, followed by the return contents. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple: three fully documented required params, complete annotations, and an output schema that already explains the return shape. The description covers purpose and output contents; only the workflow relationship to the sibling read tool is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the enum of allowed operationIds is fully enumerated in the schema, so the baseline is 3. The description adds no new meaning about projectId, accountId or operationId beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieves the exact input schema and tool version for one selected account and allowlisted read operation. The 'schema' framing distinguishes it implicitly from the sibling execution tool playground_connected_source_read, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'allowlisted read operation' implies this is a pre-flight step, but the description never says 'call this before playground_connected_source_read' or states any when-not conditions. Useful context is instead buried in the operationId parameter description ('inspect its schema before supplying arguments'), not in the tool description itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.