Skip to main content
Glama

check_agent

Verify any AI agent by name and retrieve its trust score, security grade, autonomy level, Bitcoin passport, badges, registration date, and capabilities.

Instructions

Get full profile of an AI agent: trust score, security grade, autonomy level, Bitcoin passport, badges, registration date, capabilities. Use this to verify any agent.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/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; it implies a read-only lookup through the verb 'Get' and usefully lists the data returned. It says nothing about authentication requirements, rate limits, or what happens when the agent name is unknown, which are real gaps for an unannotated tool.

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 the returned data, with no filler. The field enumeration is long but earns its place because no output schema exists.

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 simple single-parameter lookup with no output schema, the field list effectively substitutes for return-value documentation. Missing only edge-case behavior such as unknown-agent responses to be fully complete.

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 'name' parameter is already documented in the schema as 'Agent name to look up'. The description's phrase 'any agent' adds only a hint that no filtering or scoping is required beyond the name, so baseline 3 applies.

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?

States a concrete verb and resource ('Get full profile of an AI agent') and enumerates the profile fields returned, so an agent can tell what it retrieves. It does not explicitly differentiate itself from the trust/security-oriented siblings, so it stops short of a 5.

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?

'Use this to verify any agent' gives an implied usage context, but offers no when-not guidance and no explicit routing to alternatives such as security_scan or trustgate. Usage is suggested rather than defined.

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