Skip to main content
Glama
Sign In

SAID Protocol

by io.github.Jugmaster
OverviewDiscussionsAdmin

Find a registered agent

find_agent
Read-onlyIdempotent

Search SAID Protocol's registry of AI agents by name, X handle, description or wallet. Returns matching agents with verification status, trust score and profile link. Use to resolve "who is this agent" or to find a counterparty's registered wallet.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10
queryYesName, @handle, keyword or wallet fragment
verifiedOnlyNoOnly return verified agents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the searchable fields and the shape of results (verification status, trust score, profile link). It stops short of describing pagination or what happens with an empty result set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the search scope, then the return shape, then the use case. No redundant or filler wording.

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 three-parameter read-only search with full schema coverage and no output schema, the description covers purpose, inputs, and result content well. Only minor gaps remain, such as result ordering and default behavior when nothing matches.

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 description coverage is 100%, so query, limit and verifiedOnly are all documented in the schema. The description's mention of name/handle/description/wallet echoes the query field's own description and adds only the clarification that handles are X handles. Baseline 3 is appropriate.

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?

States a specific verb (search) and resource (SAID Protocol's registry of AI agents), plus the exact fields matched on (name, X handle, description, wallet) and what is returned. An agent can distinguish this from check_token/check_wallet, which are single-entity lookups rather than registry searches.

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

Usage Guidelines4/5

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

Gives concrete use cases: resolving 'who is this agent' and finding a counterparty's registered wallet. It does not explicitly state when NOT to use it or name an alternative tool, but the intent context is unambiguous.

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

All SAID Protocol toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources