Skip to main content
Glama

Verify shipped work

verify

Check one recorded action from the outside: a PR's state on GitHub and its live page, a page live and naming the product, a listing linking to the site (with its rel), a post still up (X through its embed endpoint; Reddit removals are detected when Reddit lets the check through, otherwise the recorded link counts). Free. Index requests and drafts cost nothing: a Bing index request is checked in Bing once Bing is connected (bing_connect); other index requests and drafts cannot be verified by us.

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": {
      "actionId": "<actionId>"
    },
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Adds genuine context beyond the annotations: it is 'Free', it reaches outside systems (GitHub, X embed endpoint, Bing), and it discloses detection limits such as Reddit removals only counting when 'Reddit lets the check through'. However, annotations declare readOnlyHint=false, and the description never clarifies what state the check itself writes or what the result looks like, leaving a gap between 'Check' and a non-read-only operation.

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

Conciseness3/5

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

Front-loaded with the core verb, which is good, but the middle sentence is a heavily parenthesized run-on mixing four check types with endpoint internals. The cost and unverifiable-case caveats are valuable but would read better as separate sentences.

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?

Covers the domain of verifiable vs non-verifiable action types and external dependencies, which is the hard part. But with no output schema and 0% parameter coverage, the description leaves the agent without the identifier source or any sense of what a verification result contains.

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%, so the description must carry the burden for the single required actionId — and it never mentions the parameter or says where an actionId comes from (presumably record_action or shipped). The agent knows what kinds of actions exist but not how to identify one.

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?

Opens with a specific verb and scope: 'Check one recorded action from the outside', then enumerates the concrete artifact types it can verify (PR state, live page, listing rel, post retention). An agent can tell this apart from siblings like index_status or check_content by the enumerated check types, though the distinction is not stated explicitly.

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?

Gives real when-to-use boundaries: index requests and drafts 'cannot be verified by us', and Bing index requests only work 'once Bing is connected (bing_connect)', pointing at the prerequisite sibling. It stops short of naming an alternative tool for the cases it cannot handle, so the agent is left to guess where to route those.

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.

Resources