Skip to main content
Glama

Little Works

get_person_proof

Validated / public proof for a person (validation chain: projects and related work).

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": {
      "userId": "<userId>"
    },
    "name": "get_person_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes
projectsOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it says nothing about permissions or visibility of "public" versus private proofs, whether the call is read-only, pagination, or what happens when no proof exists. The phrase "validated / public" gestures at two modes but never explains which one applies when.

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?

It is a single short fragment and thus not padded, but the fragment structure with a slash-joined "Validated / public" and a parenthetical makes it ambiguous rather than efficient. The most important information, what a proof actually is, is not front-loaded because it is never stated.

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

Completeness2/5

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

With two parameters, zero schema coverage, no annotations, and no output schema, the description is the only source of semantics and it leaves the resource definition, the meaning of both parameters, and the failure modes unexplained. A caller could not confidently invoke this tool from the definition alone.

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 explain userId and projectsOnly, and it does not. The parenthetical about projects and related work weakly hints that projectsOnly narrows the chain to projects, but that is inference rather than documentation.

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

Purpose3/5

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

The name and description together indicate a read of some per-person "proof" record, and the parenthetical hints that the proof is derived from a validation chain of projects and related work. However, "proof" and "validated / public proof" are undefined domain jargon, so an agent cannot tell concretely what resource is returned, and the description never names a contrasting sibling such as match_proof or get_project.

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

Usage Guidelines2/5

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

There is no statement of when to call this instead of match_proof, get_project, get_profile, or get_public_share_url, which are nearby names an agent would have to disambiguate from. Usage is only implied by the word "proof".

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