Skip to main content
Glama

FIDES Ecosystem Explorer

search_issuers

Read-onlyIdempotent

Search the FIDES issuer catalog for credential issuers — who issues which credentials, in which environment, with which configurations. Filter by free-text, environment, organization, VC format, credential catalog id, subject type, tags, and country. 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_issuers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page (default 0)
sizeNoPage size, max 50 (default 20)
sortNoSort field (default: displayName)
tagsNoFree-text, case-insensitive partial match on tags
orgIdNoExact organization catalog id, e.g. 'org:animo'
searchNoFree-text across id, orgId, display name, description, URLs, org name, and credential configuration fields
countryNoExact ISO country code of the issuer organization, e.g. 'NL'
vcFormatNoIssuer has a configuration with this VC format, e.g. 'sd_jwt_vc'
directionNoSort direction
environmentNoExact environment match, e.g. 'test' or 'production'
subjectTypeNoIssuer has a configuration with this subject type, e.g. 'Person'
credentialCatalogIdNoIssuer issues this FIDES credential catalog id, e.g. 'cred:eu:pid-vc-sd-jwt:sd-jwt-vc'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behaviour, so the safety profile is covered. The description adds value beyond that by disclosing the return shape ('compact, paginated list with canonical detail URLs'), which tells the agent results are paged and that detail lives elsewhere (get_issuer). It does not mention result limits or ordering behaviour beyond the sort params.

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 the purpose, followed by the filtering surface and return format. No filler, no repetition of annotation data.

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 twelve optional parameters, full schema coverage and no output schema, the description covers the essentials: what is searched, what can be filtered, and what comes back (paginated compact list with detail URLs). A note on result limits or how to follow the canonical URLs would make it fully complete.

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%, so all twelve parameters are already documented with examples in the schema. The description only restates the filter categories ('free-text, environment, organization, VC format, credential catalog id, subject type, tags, and country') without adding matching semantics or format rules, 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 gives a specific verb and resource ('Search the FIDES issuer catalog for credential issuers') and scopes it with 'who issues which credentials, in which environment, with which configurations'. This clearly separates it from the other catalog searches (credential types, organizations, relying parties), though it never explicitly names a sibling, so it falls just short of a 5.

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 only implied: an agent can infer 'use this to find issuers'. There is no statement of when to prefer it over search_organizations (a close neighbour) or get_issuer for detail retrieval, and no exclusions or prerequisites are given.

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