Skip to main content
Glama
alexfleetcommander

Agent Trust Stack MCP Server

by alexfleetcommander
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

verify_agent_identity

Validates agent identity by fetching a DID document or A2A Agent Card and checking its structure, fields, and format against relevant specifications.

Instructions

Fetch and validate an agent's identity from a DID document or A2A Agent Card.

Given a URL pointing to a DID document (did.json) or A2A Agent Card
(agent-card.json), fetches the document and validates its structure against
the relevant specification.

For DID documents: checks @context, id format, verificationMethod, service endpoints.
For Agent Cards: checks name, provider, capabilities, skills, extensions.

Requires network access to fetch the document.

Args:
    url: URL to a DID document or A2A Agent Card JSON file.
         Examples:
           - https://example.com/.well-known/did.json
           - https://example.com/.well-known/agent-card.json

Returns:
    JSON validation report with document type, validity, fields found, and any issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

No annotations provided, so description must disclose behavior. It explains the fetch-and-validate process, what is checked for each document type, and the need for network access. Does not detail error handling or security considerations, but covers key aspects.

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?

Well-structured with Args and Returns sections, clear and informative. Could be slightly more concise but still efficient for the complexity it covers.

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

Completeness5/5

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

Given the tool's complexity (validating two document types) and that an output schema exists, the description is complete. It explains input, process, and validation fields without needing to detail return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter 'url' with 0% schema description coverage. Description compensates fully by explaining it expects a URL to a DID document or Agent Card, and gives examples. This adds meaning beyond the schema's minimal definition.

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 fetches and validates an agent's identity from a DID document or A2A Agent Card, listing specific checks for each. This distinguishes it from siblings like arp_check which likely deals with ARP, not identity.

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?

Mentions requirement for network access, but does not explicitly state when to use this tool versus alternatives like get_trust_evidence or trust_stack_info. Implicitly for identity verification from URLs, but lacks explicit guidance.

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/alexfleetcommander/agent-trust-stack-mcp'

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