Skip to main content
Glama
Sign In

MolTrust MCP Server

by io.github.MoltyCel
OverviewDiscussionsAdmin

moltproof_verify

Deprecated alias of molcheck_verify; use that name. Recompute a verdict from public inputs and check its signature.

    Offline and read-only: no DID/mandate/context is fetched here.

    Args:
        agent: public agent identifier
        mandate: the public AAE Verifiable Credential
        actions: public, already-decoded on-chain actions
        signature: optional prior MolCheck signature to check

Input Schema

NameRequiredDescriptionDefault
agentYes
actionsYes
mandateYes
signatureNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / title
      Previous value: -"moltproof_verifyArguments"New value: +"verifyArguments"
    • changedOutput schema / title
      Previous value: -"moltproof_verifyOutput"New value: +"verifyOutput"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the key safety profile: 'Offline and read-only: no DID/mandate/context is fetched here.' This is meaningful beyond the schema. It stops short of describing failure behavior (e.g., signature-mismatch outcome), which keeps it from a 5.

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?

Front-loads the most decision-relevant fact (deprecation) ahead of the functional detail, and the Args block is tidy. Slightly longer than strictly necessary due to the enumerated arg list, but every line earns its place.

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?

An output schema exists, so return values need not be explained, and the description covers the offline/read-only behavior plus all four undocumented params. Complete enough for an agent to call it correctly, though no guidance on the signature result semantics is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 compensate, and it documents all four parameters ('public agent identifier', 'the public AAE Verifiable Credential', 'public, already-decoded on-chain actions', 'optional prior MolCheck signature'). It conveys the semantic role of each param but no format or syntax detail.

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?

States a specific verb+resource ('Recompute a verdict from public inputs and check its signature') and immediately differentiates itself from siblings by naming the canonical tool molcheck_verify. An agent can tell exactly what this does and that it is a deprecated alias without opening any schema.

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?

Explicitly routes the agent away from this tool ('Deprecated alias of molcheck_verify; use that name'), which supplies the key when-not-to-use / alternative guidance. It does not fully spell out when the canonical verify is appropriate versus the many other *_verify siblings, so it falls short of a 5.

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

All MolTrust MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources