Skip to main content
Glama

mt_check_badge

Read-only

Check whether an agent is badge-verified by MolTrust using its DID, returning a simple yes/no plus tier and expiry details.

Instructions

Quick check: is this agent badge-verified by MolTrust?

Returns a simple yes/no with tier and expiry info.

Args: did: The DID of the agent to check

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": "<did>"
    },
    "name": "mt_check_badge"
  }
}

Input Schema

NameRequiredDescriptionDefault
didYesThe DID of the agent to check, e.g. did:moltrust:a1b2c3d4e5f60718

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / did / description
      Added value: +"The DID of the agent to check, e.g. did:moltrust:a1b2c3d4e5f60718"
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe, non-mutating lookup, so the description's burden is lighter. It adds that the result is a simple yes/no plus tier and expiry, but says nothing about error behavior for invalid DIDs, authentication requirements, or rate limits — and with an output schema present, the return-value detail is largely duplicate information.

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?

The description is short and front-loads the core question before the return summary. The trailing 'Args' section is redundant given full schema coverage and could be dropped, but overall there is no padding or bloat.

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-only verification call with an output schema and explicit readOnlyHint, the description covers what the tool answers and roughly what comes back. It stops short of covering edge cases like unknown DIDs or distinguishing itself from sibling badge tools, which keeps it from a 5.

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?

There is a single required parameter with 100% schema description coverage, including a concrete DID example, so the schema already does the heavy lifting. The 'Args' block merely restates the schema text verbatim ('The DID of the agent to check') without adding format, resolution, or validation semantics, which is the baseline 3 case.

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 states a specific verb and resource ('is this agent badge-verified by MolTrust?') and frames it as a 'quick check', which distinguishes it in spirit from heavier lookups. It does not name or contrast with the obvious sibling mt_get_badge, so an agent must infer the difference from the word 'quick' alone.

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?

Usage is only implied: the 'Quick check' framing suggests a lightweight yes/no lookup rather than a full badge retrieval, which is useful signal. However, there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. mt_get_badge), and no statement about behavior for an unknown or unregistered DID.

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