Skip to main content
Glama
Sign In
deusproof-mcp

deusproof-mcp

by Abracadabrastartup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

verify_certificate

Verify a certificate by ID to confirm a creation was truly timestamped: returns score, tier, hashes, Bitcoin anchor and ledger status.

Instructions

Verify a certificate by id: score, tier, hashes, Bitcoin anchor and ledger status. Use to confirm a creation was really timestamped, and when.

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": {
      "certificate_id": "<certificate_id>"
    },
    "name": "verify_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
certificate_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.6/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 burden, and it does disclose the shape of the response (score, tier, hashes, Bitcoin anchor, ledger status), which is valuable given there is no output schema. However, it never states the operation is read-only, what happens with an unknown or unanchored id, or what an anchor-pending state looks like.

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?

Two sentences, front-loaded with the action and then the use case; nothing is redundant. The internal line break and run-on field list are cosmetic blemishes rather than wasted content.

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?

For a single-parameter read tool with no output schema, the definition supplies the return fields and a use case, which is close to sufficient. The residual gaps are error behavior and id provenance, both minor for a verification lookup.

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 description coverage is 0% for the single required certificate_id, so the description should compensate but only adds the phrase 'by id'. It does not say where the id comes from (presumably the creation call) or what format it takes, leaving the one parameter only slightly clarified.

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 uses a specific verb+resource ('Verify a certificate by id') and enumerates what verification yields: score, tier, hashes, Bitcoin anchor and ledger status. It is clearly the read-side counterpart of creation tools, though it never names a sibling such as birth_certificate or certify_creation to disambiguate.

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?

'Use to confirm a creation was really timestamped, and when' gives a clear triggering scenario, which is the strongest part of the definition. It stops short of exclusions or explicit alternatives — an agent must infer on its own whether birth_certificate would be the better call in a given situation.

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