Skip to main content
Glama

FIDES Ecosystem Explorer

get_relying_party

Read-onlyIdempotent

Get full details of a single FIDES relying party by its catalog id (from search_relying_parties), e.g. 'air-new-zealand'.

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": {
      "id": "<id>"
    },
    "name": "get_relying_party"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRelying party catalog id, e.g. 'air-new-zealand'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only that the result is 'full details' of one entity plus where the id comes from, without describing result shape or not-found behavior.

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?

One tightly written sentence with the resource and lookup key front-loaded and no redundant wording. Every clause earns its place by identifying the entity, the key, and the source of that key.

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 one-parameter read-only lookup with full annotation coverage, the definition contains what an agent needs to call it correctly. The only minor gap is that 'full details' does not hint at the shape of the returned record, and no output schema exists to cover that.

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% and the single parameter is already documented with the same example value ('air-new-zealand'). The description restates rather than adds meaning, so the baseline of 3 applies.

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?

The description gives a specific verb ('Get full details'), a specific resource ('a single FIDES relying party'), and the locating key ('its catalog id'), and it explicitly names search_relying_parties as the origin of that id. That is enough for an agent to distinguish this id-lookup tool from the sibling search tool without opening either 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?

Usage context is clear: call this after obtaining a catalog id from search_relying_parties. No explicit when-not guidance or mention of what to do when no id is known, but the dependency on the search tool implicitly covers that path.

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