Skip to main content
Glama

FIDES Ecosystem Explorer

search_relying_parties

Read-onlyIdempotent

Search the FIDES relying party catalog for verifier websites and services that accept verifiable credentials. Filter by free-text, country, owning organization, readiness, status, interaction mode, sector, and accepted credential format. Returns a compact, paginated list with canonical detail URLs.

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

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page (default 0)
sizeNoPage size, max 50 (default 20)
sortNoSort field
orgIdNoOwning organization id, e.g. 'org:air-new-zealand'
searchNoFull-text search on name, description, provider, website, or accepted credentials
sectorNoComma-separated sector codes (OR), e.g. 'public_sector,mobility'
statusNoComma-separated status values (OR): development, beta, live, deprecated
countryNoISO 3166-1 alpha-2 country code, e.g. 'NL'
featuredNoWhen true, only featured relying parties
vcFormatNoComma-separated accepted credential formats (OR), e.g. 'sd_jwt_vc,mdoc'
directionNoSort direction
readinessNoComma-separated readiness levels (OR): technical-demo, use-case-demo, production-pilot, production
interactionModeNoInteraction mode filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds value beyond that by disclosing the return shape (compact, paginated list), the presence of canonical detail URLs that feed the get_* tools, and that results are filterable/sortable — meaningful because no output schema exists. It stops short of stating rate limits or auth requirements, but for a read-only search that is a minor gap.

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?

Three sentences, front-loaded with purpose and ending with the return contract, with no filler. The middle sentence enumerates eight filter categories that largely restate the schema properties, which is a minor redundancy, but it functions as a quick capability summary rather than waste.

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 13 optional parameters, no output schema, and full schema description coverage, the description supplies exactly the two things structured fields cannot: what the resource is and what the response looks like (paginated, compact, links to detail). Only the relationship to sibling tools (search vs get_relying_party, and the other search_* catalogs) is under-specified, which keeps it from a 5.

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% and the schema already documents enum values, the comma-separated OR semantics for sector/status/vcFormat/readiness, the ISO country code format, and pagination defaults. The description only names the filter categories in prose, adding no syntax or default information beyond what the schema provides, so the baseline 3 applies.

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?

The description uses a specific verb and resource — 'Search the FIDES relying party catalog for verifier websites and services that accept verifiable credentials' — which is far more informative than the name alone and clarifies what a 'relying party' is in this domain. It implies the search/get split by mentioning canonical detail URLs, but never names get_relying_party or the generic search tool, so full sibling differentiation is left to inference.

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?

Usage is implied rather than stated: the agent can infer this is the filtered-listing entry point because of the filter enumeration and the 'compact, paginated list with canonical detail URLs' output hint. There is no explicit 'use this when... / use get_relying_party instead when...' guidance and no exclusions or prerequisites, leaving the search-vs-get choice 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