Skip to main content
Glama
Sign In
digeguigui

digeguigui

by Gaoshan0971
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

verify_provenance

Check reptile pet authenticity: enter anchor ID to receive breed, birth date, and Git-verified certificate of provenance.

Instructions

扫码验证爬宠身份证 — 输入锚定ID，返回品种/出生时间/Git存证哈希

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": {
      "anchor_id": "<anchor_id>"
    },
    "name": "verify_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
anchor_idYes爬宠身份证锚定ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses what the tool returns (breed, birth time, Git hash) but does not mention side effects, authentication needs, or error conditions. Since no annotations are provided, the description carries the full burden and is only partially transparent.

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?

The description is a single, front-loaded sentence that efficiently conveys purpose and return data. No wasted words.

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?

The tool has one parameter and no output schema. The description lists three return items but does not specify their format or structure, leaving some ambiguity about the exact output.

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?

The schema covers 100% of the parameter with a clear description. The tool description only restates the parameter ('input anchor ID') without adding new semantic information beyond the schema.

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 clearly states the tool's action ('verify pet ID') and specifies the return data (breed, birth time, Git hash). It distinguishes from sibling tools like get_species_profile or identify_turtle, which serve different purposes.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it.

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

Deploy Server

Other Tools