Skip to main content
Glama

FIDES Ecosystem Explorer

search

Read-onlyIdempotent

Search across all FIDES catalogs (wallets, credential types, organizations, issuers) with a free-text query. Returns a list of results with ids and canonical URLs; use the fetch tool with a result id to retrieve full details.

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": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text query to search across all FIDES catalogs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are summaries with ids and canonical URLs, not full records, which shapes how an agent consumes the output. It stops short of disclosing pagination, result limits, or how matches are ranked across catalogs.

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?

Two sentences, front-loaded with scope and immediately followed by the workflow handoff to `fetch`. No filler, no restatement of the title, and the most decision-relevant information comes first.

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?

With no output schema, the description correctly compensates by describing the return shape (list of results with ids and canonical URLs) and how to expand them. For a one-parameter broad search tool this is close to complete; only the absence of any note on result volume or pagination keeps it from the top score.

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% with a single required `query` parameter already documented in the schema. The description restates 'free-text query' without adding any semantics the schema lacks, such as whether field-qualified syntax, quoted phrases, or partial matching are supported. Baseline 3 applies since the schema carries the parameter definition.

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 specific verb and resource: free-text search across all FIDES catalogs, and enumerates the entity types covered (wallets, credential types, organizations, issuers). The 'across all catalogs' phrasing implicitly differentiates it from the per-catalog siblings like search_wallets and search_issuers, though the enumeration omits relying parties and use cases that siblings cover.

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?

Explicitly names the follow-up tool and the condition for it: use `fetch` with a result id to get full details, which establishes a clear two-step search-then-fetch workflow. It does not state when an agent should prefer this broad search over scoped siblings such as search_issuers, leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources