Skip to main content
Glama

test_source

Dry-run a source configuration before creation: poll connectors perform one live poll and return a sample, while push connectors return their ingest endpoint, so you can verify the config works.

Instructions

Dry-run a source config without creating it: poll connectors do one live poll and return a sample; push connectors return their ingest endpoint. Use before create_source to check the config works.

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": {
      "name": "<name>",
      "connector": "<connector>",
      "config": "<config>"
    },
    "name": "test_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pollNo5s
configYes
connectorYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the whole burden and does meaningful work: it discloses that this is non-creating, and — importantly — that a 'dry run' for poll connectors still performs one live poll, which is a real external side effect an agent must know about. It also differentiates return behavior by connector type. It does not say whether the live poll consumes/advances anything on the source or what permissions are needed, which keeps it below a 5.

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 sentences, front-loaded with the dry-run framing, then the connector-type divergence, then the placement relative to create_source. No filler and nothing repeated from the title or schema.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the description does cover the key behavioral split. However, for a 4-parameter tool with a nested free-form config and zero schema documentation, the description leaves the parameters and the side effects of the live poll unaddressed — enough gaps that an agent could call it with a wrong config shape or misunderstand what the poll actually does.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters (name, connector, config, poll), and the description does not compensate: 'name' and 'poll' are never mentioned, 'connector' is only alluded to via the poll/push distinction, and 'config' is only described as the thing being tested. The 'poll' default of 5s and the free-form nested config object remain unexplained anywhere.

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

Purpose5/5

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

States a specific verb and resource ('Dry-run a source config') and immediately distinguishes itself from create_source by saying 'without creating it'. The second clause goes further and explains the two divergent behaviors (poll connectors sample, push connectors return an endpoint), so an agent knows exactly what this tool produces.

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

Usage Guidelines4/5

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

Explicit sequencing guidance: 'Use before create_source to check the config works' names the sibling and the condition that selects this tool. It stops short of the inverse case (when to skip the dry run, e.g. already-validated configs, or when to prefer discover_source), so not a full when/when-not pair.

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