Skip to main content
Glama
agents-registry-com

Agents Registry MCP Server

agents_registry_verify

Verify digital signatures from agents to confirm message authenticity, either through the registry or using a known public key.

Instructions

Verify that a message was signed by a specific agent. Can verify via the registry or locally with a known public key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesThe original message that was signed
signatureYesThe signature to verify (base64 encoded)
originYesThe origin/domain claiming to have signed the message
keyIdNoSpecific key ID to verify against (optional)
localOnlyNoIf true, verify locally without contacting the registry
publicKeyNoPublic key for local verification (required if localOnly=true)
Behavior2/5

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

No annotations provided; description only mentions basic verification modes. Does not disclose side effects, error handling, auth requirements, or output format expected from a verification operation.

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?

Single sentence front-loaded with action verb 'verify'. Efficient and to the point with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema; description fails to mention what the tool returns (e.g., boolean, details). Two modes are mentioned but not elaborated, leaving agent uncertain about behavior and results.

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 covers 100% of parameters. Description adds context about two verification modes but doesn't enrich parameter meanings beyond schema. Baseline 3 for high schema coverage.

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?

Description clearly states it verifies a signed message by an agent, with two verification methods (registry or local). Differentiates from sibling tools focused on inbox, lookup, reply, send, and whoami.

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?

No guidance on when to use which verification method, prerequisites, or when to avoid this tool. Lack of context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agents-registry-com/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server