Skip to main content
Glama

FIDES Ecosystem Explorer

search_use_cases

Read-onlyIdempotent

Search the FIDES use case catalog for real-world verifiable credential deployments and demos (e.g. age verification, mobile driver's license login, digital travel credentials). Filter by free-text, country, sector, credential format, interaction mode, tag, and production status. 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_use_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoComma-separated tags (OR), e.g. 'age-verification,travel'
pageNoZero-based page (default 0)
sizeNoPage size, max 50 (default 20)
sortNoSort field
searchNoFull-text search on title, summary, organization, or tags
sectorNoComma-separated sector codes (OR), e.g. 'public_sector,mobility'
countryNoISO 3166-1 alpha-2 country code, e.g. 'NL'
vcFormatNoComma-separated credential formats used (OR), e.g. 'sd_jwt_vc,mdoc'
directionNoSort direction
interactionModeNoComma-separated interaction modes (OR): proximity, remote, both
productionDeploymentNoFilter on whether the use case is in production

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds value on top by disclosing the return shape ('compact, paginated list with canonical detail URLs'), which tells the agent results are summaries needing a follow-up fetch. It does not mention result caps beyond the schema's size limit or what an empty result looks like, 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?

Three sentences, front-loaded with the purpose, then filters, then return shape — no filler or marketing language. The parenthetical example list is the only slightly expendable element, though it does usefully define the domain of a 'use case'.

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 an 11-parameter, all-optional search tool with no output schema, the description covers purpose, filterable dimensions and the shape of the response, which is what an agent needs to call it correctly. Gaps are minor: no guidance on combining facets or on when to escalate from a search hit to a detail tool.

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 all 11 parameters are already documented including OR semantics, ISO codes and defaults. The description only enumerates the filter facets at a high level ('free-text, country, sector, credential format, interaction mode, tag, and production status') and omits sort, direction, page and size, adding no syntax or value-format detail beyond the schema. 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?

States a specific verb and resource ('Search the FIDES use case catalog') and scopes the content with real examples of what a use case is (age verification, mDL login, digital travel credentials). The mention of returning 'canonical detail URLs' implicitly separates it from the detail-fetching siblings, but no sibling is named, so the distinction is inferential rather than explicit.

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 broad discovery entry point and that detail URLs lead to per-item lookup tools. There is no explicit when-to-use/when-not-to-use guidance, no note about empty results, and no statement about how the facets combine (AND across facets vs OR within a facet).

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