Skip to main content
Glama

Verify endpoint

verify_endpoint
Read-onlyIdempotent

Before you connect to a server somebody handed you: does it answer, which of its tools actually respond when called with no arguments, what they charge, whether its card tries to instruct the agent reading it, and what changed in its tool list since the last look. Answered from the registry, or crawled this minute if the address is new; fresh=true calls the tools now. Every answer has a receipt address you can cite.

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": {
      "url": "<url>"
    },
    "name": "verify_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe server to check: an MCP endpoint, an A2A agent card or a bare https domain
freshNoCall the tools now rather than answering from the last look (rationed per caller)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / description
      Added value: +"The server to check: an MCP endpoint, an A2A agent card or a bare https domain"
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), and the description adds genuine behavior beyond them: answers may come from the registry (potentially stale) or be crawled fresh, new addresses are crawled by default, and every response carries a citable receipt address. It does not discuss failure/timeout behavior for unreachable endpoints, which keeps it off 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 decision trigger, then the enumerated checks, then the sourcing and freshness mechanics. Every clause carries distinct information; nothing is filler.

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?

With no output schema, the description still conveys what comes back (answers to five specific questions plus a receipt address) and where the data originates, which is what an agent needs to interpret results. The absence of any note on what happens when the endpoint is unreachable is the one meaningful gap.

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 both parameters are self-documenting ('url' and 'fresh' with its rationing caveat), so the baseline is 3. The description adds minor value by explaining that a new address is crawled automatically and that fresh actually invokes the remote tools, but that largely restates the schema's 'rather than answering from the last look'.

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?

The description names a specific verb (verify) and enumerates exactly what it checks: reachability, which tools respond with no arguments, pricing, prompt-injection attempts in the card, and tool-list drift since last look. That is a concrete, distinguishable scope an agent can match against siblings like agent_liveness or agent_trust without opening a schema.

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?

It gives a clear trigger condition — 'Before you connect to a server somebody handed you' — that maps directly to the moment an agent needs this check. It stops short of naming alternatives or stating when not to use it (e.g., versus a lighter liveness-only check), so it is clear context rather than full routing guidance.

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.