Skip to main content
Glama

FIDES Ecosystem Explorer

search_wallets

Read-onlyIdempotent

Search the FIDES wallet catalog for digital identity wallets. Filter by free-text query, organization, type, platform, supported credential (VC) format, capabilities, interoperability profiles, open-source, and 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_wallets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page (default 0)
sizeNoPage size, max 50 (default 20)
sortNoSort field (default: displayName)
typeNoWallet type
orgIdNoExact organization catalog id, e.g. 'org:animo'
searchNoFree-text match on wallet name, description, provider, or id
statusNoComma-separated status: 'development,beta,production,deprecated'
vcFormatNoComma-separated VC formats, e.g. 'sd_jwt_vc,mdoc,vcdm_2_0'
directionNoSort direction
platformsNoComma-separated platforms, e.g. 'iOS,Android,Web'
protocolsNoComma-separated issuance/presentation protocols
openSourceNoOnly open-source wallets
capabilitiesNoComma-separated capabilities: 'holder,issuer,verifier'
interoperabilityProfilesNoComma-separated profiles, e.g. 'EUDI Wallet ARF,DIIP v5'

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 needs no restating. The description's useful addition is the return shape ('compact, paginated list with canonical detail URLs'), which matters because there is no output schema. It says nothing about empty-result behavior, total counts, or how multiple filters combine (AND vs OR), which would have raised this above a 3.

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, zero filler. The purpose and filter surface are front-loaded, and the return-shape sentence follows immediately with the information an agent cannot get from the schema.

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 14-parameter, all-optional search tool with no output schema, the description supplies the two things structure cannot: the scope of the filter surface and the shape of the response (compact, paginated, detail URLs). It leaves minor gaps around filter combination logic and result-count metadata, but nothing essential for correct invocation is missing.

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 every parameter is already documented with examples and enums (e.g. orgId 'org:animo', vcFormat 'sd_jwt_vc,mdoc,vcdm_2_0'). The description only re-lists filter categories and omits sort, direction, page, size, and protocols entirely, adding no syntax or semantics 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?

The description names a specific verb and resource ('Search the FIDES wallet catalog for digital identity wallets') and enumerates the filterable dimensions, so an agent immediately knows this is the catalog search endpoint for wallets rather than the sibling searches for credential types, issuers, or organizations. It stops short of explicitly contrasting itself with get_wallet, relying instead on the hint that results carry 'canonical detail URLs'.

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?

Usage context is clear: this is the broad filtered-discovery tool, and results are 'compact' with detail URLs, which implies following a detail call (get_wallet) once a wallet is identified. There are no explicit when-not conditions or named alternatives, so it falls short of a 5.

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