Skip to main content
Glama

Test a source

test_source
Read-only

Checks whether a connected source opens and explains why it fails, helping diagnose connection issues.

Instructions

Test a connected source: says whether it opens, and if not, why.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare a safe, read-only, closed-world operation, and the description correctly reinforces that by framing it as a non-mutating test. Beyond that it only hints at return semantics ('whether it opens, and if not, why') without saying how the reason is reported or whether failures surface as errors versus a result field, which matters since there is no output schema.

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?

One front-loaded sentence with the verb, resource, and outcome in order, and no wasted wording. Everything stated earns its place.

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?

For a simple one-parameter read-only tool the behavioral framing is largely sufficient, but with no output schema and 0% schema description coverage, the definition leaves the required 'name' argument and the shape of the failure reason unspecified. Small but real gaps remain.

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?

The schema has a single required parameter 'name' with 0% description coverage, so the description must carry the meaning and it does not: it never says the parameter is the source's name or what form that identifier takes. An agent must guess what to pass.

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?

The description names a specific verb and resource ('Test a connected source') and clarifies the outcome ('says whether it opens, and if not, why'), which separates it from describe_source and add_source/remove_source. It stops short of explicitly naming a sibling to differentiate against, so a 4 rather than a 5.

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 usage is only implied: an agent can infer you run this to verify a source is reachable before querying it. There is no statement of when to prefer this over describe_source or list_sources, and no prerequisites or exclusions are given.

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