Skip to main content
Glama

FIDES Ecosystem Explorer

get_use_case

Read-onlyIdempotent

Get full details of a single FIDES use case by its catalog id (from search_use_cases), e.g. 'age-verification-online-purchase'.

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_use_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUse case catalog id, e.g. 'age-verification-online-purchase'

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 is fully covered by structured data. The description adds only that the response is 'full details' rather than a summary — useful but thin, and with no output schema the agent still doesn't know which fields come back.

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 sentence, front-loaded with the verb and resource, with the retrieval hint and a concrete example packed into the same line. Nothing is redundant or padded.

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 complete annotations, the description covers what the tool does and how to obtain the key. The remaining gap is the shape of the returned 'full details', which is only weakly characterized in the absence of an output schema.

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 the single 'id' parameter already carries its own description and example, so the schema does the heavy lifting. The description's only added meaning is where the id comes from (search_use_cases), which justifies the baseline 3 rather than a higher score.

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 ('Get full details of a single FIDES use case') and states the lookup key is the catalog id. Naming search_use_cases as the origin of the id implicitly separates this detail-fetch from the search sibling, though it never explicitly contrasts their behaviors.

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 parenthetical '(from search_use_cases)' establishes a clear two-step workflow: search first, then fetch by id. There are no explicit exclusions or when-not-to-use conditions, but the usage context is unambiguous for a simple keyed lookup.

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