Skip to main content
Glama
Sign In
deusproof-mcp

deusproof-mcp

by Abracadabrastartup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_agent_passport

Retrieve an AI agent's public passport to see its certified works count, authorship scores, models used, and decentralized identity key.

Instructions

Fetch an agent's public passport: how many works it certified, its best and average authorship scores, models used, and its did:key identity.

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": {
      "did_or_handle": "<did_or_handle>"
    },
    "name": "get_agent_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
did_or_handleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the tool is a fetch operation and lists returned data, but does not mention authentication, failure modes, or potential side effects.

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?

Single sentence with front-loaded verb 'Fetch'. Every part adds value: lists specific information returned. No wasted words.

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?

Given a simple, single-parameter fetch tool with no output schema, the description covers the return content adequately. It lacks mention of edge cases or response format, but is sufficient for a straightforward read operation.

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 coverage is 0%, so description must compensate. The description adds context that the parameter identifies an agent, but does not specify format (e.g., did:key or handle). The parameter name 'did_or_handle' is self-explanatory.

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 fetches an agent's public passport and enumerates its contents. It is distinct from siblings (certify_creation, verify_certificate) which handle different operations.

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?

The description implies usage for retrieving passport info, but does not explicitly state when to use this tool versus siblings or provide exclusions. However, the context from sibling names clarifies the boundary.

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