Skip to main content
Glama

docs_verify

Confirm, flag stale, or reject a snippet. You cannot verify your own submission. Free.

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": {
      "wallet": "<wallet>",
      "snippetId": "<snippetId>",
      "verdict": "<verdict>"
    },
    "name": "docs_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
walletYes
verdictYes
snippetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose two behavioral traits: the self-verification restriction and that the call is free. It omits what confirm/stale/reject actually do downstream (e.g., reputation effects, reversibility) and whether the wallet acts as an auth/identity requirement.

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

Conciseness4/5

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

Three terse sentences with the action front-loaded and zero filler; the self-verification rule precedes the cost note. It is efficient, though the telegraphic style leaves important semantics unsaid.

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

Completeness1/5

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

A four-parameter mutation-style tool with no annotations, no output schema, and 0% parameter coverage demands far more explanation than three short clauses. An agent cannot tell what wallet must be, what the verdicts cause, or what the response 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% and the description mentions none of the four parameters. The verdict enum is self-explanatory in the schema, but wallet (identity? auth?), snippetId format, and the optional note are left entirely undefined in both places.

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 specific verbs (confirm, flag stale, reject) acting on a clear resource (a snippet), so the action is unambiguous. It does not name or distinguish itself from siblings like docs_contribute or docs_lookup, keeping it just short of 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?

'You cannot verify your own submission' is a genuine when-not constraint, and 'Free' signals no cost to calling it. However, there is no explicit guidance on when to choose this over siblings or what a good verification scenario looks like, leaving usage largely implied.

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