Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

identity__resolve_agent

Resolve an agent's identity by agent ID or DID to retrieve its full public registration.

Instructions

[identity — verifiable agent identity + capability discovery] Resolve an identity by agent_id or DID to its full public registration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "identity__resolve_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
didNo
agent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.12
  2. Removedv0.1.11
  3. Changed4 schema fields changedv0.1.9
    • removedInput schema / properties / agent_id / title
      Removed value: -"Agent Id"
    • removedInput schema / properties / did / title
      Removed value: -"Did"
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"resolve_agentArguments"
  4. Changed4 schema fields changed
    • addedInput schema / properties / agent_id / title
      Added value: +"Agent Id"
    • addedInput schema / properties / did / title
      Added value: +"Did"
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"resolve_agentArguments"
  5. Changed4 schema fields changed
    • removedInput schema / properties / agent_id / title
      Removed value: -"Agent Id"
    • removedInput schema / properties / did / title
      Removed value: -"Did"
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"resolve_agentArguments"
  6. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so description carries full burden. It discloses a read-like operation that returns public registration, but lacks details on error handling, authorization needs, or rate limits. Adequate but not rich.

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 with clear category prefix. No wasted words, but lacks structured sections for different aspects.

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

Completeness3/5

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

Given 2 params, no output schema, and no annotations, the description is minimally adequate. It explains the primary function but could detail what 'full public registration' includes and any constraints (e.g., DID format). Siblings exist but not differentiated.

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

Parameters2/5

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

Schema coverage is 0%. Description adds that either 'agent_id' or 'DID' can be used for resolution, which is helpful, but does not clarify requiredness, format, or behavior when both provided. Minimal value beyond schema.

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 uses specific verb 'resolve' and resource 'identity', and specifies the resolution methods (by agent_id or DID). It distinguishes from siblings like register_agent and discover_agents by focusing on getting full public registration.

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?

Description implies usage context (when you have an agent_id or DID and need public registration) but provides no explicit guidance on when to use vs alternatives like describe_agent, nor any exclusions or prerequisites.

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

Deploy Server

Other Tools