Skip to main content
Glama

FIDES Ecosystem Explorer

search_organizations

Read-onlyIdempotent

Search the FIDES organization catalog for organizations and their ecosystem roles (issuer, credential, wallet, relying party). This is also the catalog for Qualified Trust Service Providers (QTSPs) and the qualified trust services they may provide per the EU eIDAS Trust List — e.g. to answer 'which QTSPs may issue QEAAs?' use trustService='QEAA' (optionally with certification='qtsp'). Filter by free-text, country, role, certification, and trustService. Search also matches Pro plan offerings. Results include catalogTier, tags and offerings when present (Pro), plus certification and trust-service codes. 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_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page (default 0)
roleNoEcosystem role filter
sizeNoPage size, max 50 (default 20)
sortNoSort field
searchNoFull-text search on name, legal name, description, identifiers, certifications, and Pro plan offerings
countryNoISO 3166-1 alpha-2 country code, e.g. 'NL'
directionNoSort direction
trustServiceNoComma-separated qualified trust-service codes carried by a QTSP certification (OR semantics). Use 'QEAA' to find QTSPs that may issue Qualified Electronic Attestations of Attributes; other codes include Q_WAC, Q_CERT_ESIG, Q_CERT_ESEAL, Q_TIMESTAMP.
certificationNoComma-separated certifications, e.g. 'iso27001,qtsp'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds non-obvious return behavior: a compact, paginated list with canonical detail URLs, and conditional fields (catalogTier, tags, offerings) that appear only for Pro entries. Rate limits or total-count behavior are not mentioned, which keeps it below a 5.

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?

Front-loads the purpose and the headline example before listing filters and result shape, and every sentence carries information. It is dense but somewhat over-packed into three long sentences, with mild redundancy between the QTSP framing and the result-fields sentence.

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 9-parameter search tool with no output schema, the description supplies the missing return contract (paginated compact list, canonical URLs, conditional Pro fields) and the domain meaning of trust services. Remaining gaps are minor, such as total-result or empty-result behavior.

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%, including the trustService and certification semantics and OR semantics, so the baseline is 3. The description reinforces the QTSP/QEAA query pattern and the trustService+certification combination, but adds little beyond what the schema already states for each parameter.

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 ('Search the FIDES organization catalog') plus the scope it covers: ecosystem roles, QTSPs/eIDAS trust services, and Pro plan offerings. It is clearly distinguishable from generic search tools by naming the organization catalog, though it never explicitly contrasts itself with role-specific siblings like search_issuers or search_wallets, which cover overlapping ground.

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 a concrete when-to-use scenario ('to answer "which QTSPs may issue QEAAs?" use trustService=QEAA, optionally with certification=qtsp'), which is unusually actionable. It stops short of excluding cases or telling the agent when to prefer search_issuers / search_relying_parties instead.

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