Skip to main content
Glama

openentity_mandate_verify

Verify a mandate/1 against its owner's key log and status URL: who issued it, for which agent, the limits and scope, and whether it is still active. Pass agent_did to also check the agent presenting it.

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": {
      "mandate": "<mandate>"
    },
    "name": "openentity_mandate_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
mandateYes
agent_didNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden. It does reveal the verification mechanism (owner's key log plus a status URL), which implies an external lookup that may fail or be stale, and the phrasing implies a read-only check. It omits failure modes, what a negative result looks like, and any trust or network assumptions behind dereferencing the status URL, so meaningful gaps remain.

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?

Two sentences, no preamble, front-loaded with the verb and resource. The colon-delimited list of checked attributes is dense rather than redundant, and the optional-parameter hint comes last in logical order.

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?

There is no output schema, and the description sketches the return contents (issuer, agent, limits, scope, active flag), which is what an agent needs to decide whether to call it. Completeness is slightly undercut by the ambiguity of whether those items are returned values or merely things inspected, and by the untyped nested mandate object.

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% and the mandate parameter is a free-form object with additionalProperties, so the description must compensate. It clarifies what agent_did means ('the agent presenting it') and implies the mandate carries an owner and status URL reference. The internal structure of the mandate object itself remains undefined, which is the largest semantic hole.

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 names a specific verb (verify) and resource (mandate/1) and enumerates what is checked: issuer, bound agent, limits, scope, and active status. That is far more concrete than the name alone. It does not, however, distinguish this from sibling tools such as openentity_verify or openentity_mandate_covers, leaving the agent to infer which verification entry point applies.

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

Usage Guidelines3/5

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

The only usage guidance is conditional and parameter-level: 'Pass agent_did to also check the agent presenting it.' That tells the agent when to supply an optional argument, but there is no statement of when this tool is preferred over openentity_verify, openentity_mandate_covers, or openentity_present, and no exclusions or prerequisites (e.g., whether the mandate's owner must be resolvable first).

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.