Skip to main content
Glama

mt_get_badge

Read-only

Check an agent's Verified by MolTrust badge status and retrieve its trust score, grade, issue/expiry dates, and embeddable SVG URL.

Instructions

Get the Verified by MolTrust badge status for an agent.

Returns badge tier, trust score, grade, issue/expiry dates, and embeddable SVG URL.

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_get_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

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the description's main added value is enumerating the returned data (tier, trust score, grade, issue/expiry dates, SVG URL). It says nothing about auth requirements, rate limits, or what happens when a DID has no badge, which would be the genuinely useful additions.

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 purpose and return values are front-loaded in two tight sentences. The trailing Args block duplicates the schema and could be dropped, but overall it is lean.

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?

With one parameter, full schema coverage, a readOnly annotation, and an output schema explaining return values, the definition covers what an agent needs to invoke it. The remaining gap is routing versus the near-identical mt_check_badge sibling.

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 100% and the single 'did' parameter is already documented with an example in the schema; the description's 'Args: did: The DID of the agent to check' merely restates it. Baseline 3 applies since the schema carries the semantics.

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 opens with a concrete verb and resource: 'Get the Verified by MolTrust badge status for an agent,' and lists the returned fields. It does not, however, distinguish this from the close sibling mt_check_badge, leaving the agent to guess which read tool to call.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no indication of how this differs from mt_check_badge, mt_issue_badge, or mt_get_trust_score. The agent must infer the correct choice from tool names alone.

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