Skip to main content
Glama

FIDES Ecosystem Explorer

get_wallet

Read-onlyIdempotent

Get full details of a single FIDES wallet by its organization id and wallet id (from search_wallets). Returns the complete record including provider, supported credential formats, protocols, key storage, certifications, and links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orgId": "<orgId>",
      "walletId": "<walletId>"
    },
    "name": "get_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYesOrganization catalog id, e.g. 'org:animo'
walletIdYesWallet id within the organization (the 'id' field)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 the safety profile is covered. The description adds value beyond that by enumerating the record's content (provider, credential formats, protocols, key storage, certifications, links), which substitutes for the absent output schema.

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 action and the identifiers, no filler or restated title. Every clause contributes either identification guidance or return-content expectations.

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 two-parameter read tool with full annotation coverage and no output schema, listing the returned fields makes it callable with confidence. The only gap is unspecified failure behavior for an unknown orgId/walletId.

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% and both parameters are already documented with format examples, so the schema does the heavy lifting. The description adds only the provenance hint that walletId comes from search_wallets, which is a marginal gain over the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get full details of a single FIDES wallet') and pins the two identifying keys. The parenthetical '(from search_wallets)' makes clear this is the detail lookup that pairs with the sibling search tool, so an agent can distinguish it without opening the schema.

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?

The '(from search_wallets)' note gives explicit chaining guidance: search first, then fetch details by id. It does not state when not to use it or what happens with an invalid/unknown id, so it stops short of full when/when-not coverage.

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