Skip to main content
Glama

FIDES Ecosystem Explorer

explain_terms

Read-onlyIdempotent

Look up official FIDES glossary definitions for the terminology used across the catalogs and filters (credential formats such as SD-JWT-VC and mDL/mDoc, interaction modes such as proximity and remote, interoperability profiles, issuance/presentation protocols, DID methods, key storage, etc.). Call with no arguments to retrieve the complete glossary, or pass specific terms to define just those. Each definition includes a detailUrl to its entry on the FIDES glossary page — cite that as the source. Use this for conceptual questions like 'what is the proximity flow?' or 'which credential formats are there?'.

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": "explain_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
termsNoOptional list of specific terms to define (case-insensitive), e.g. ['proximity', 'SD-JWT-VC', 'OpenID4VP']. Omit to return the full FIDES glossary (useful for questions like 'which credential formats exist?').

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavioral context beyond them: that definitions carry a `detailUrl` which should be cited as the source, and that case-insensitive matching applies to requested terms.

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?

Front-loaded with purpose, then call modes, then citation guidance and example questions. It is somewhat long due to the parenthetical enumeration of term categories, but every sentence still carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema, the description covers purpose, both invocation modes, the shape of returned items (definition + detailUrl) and citation expectations. Nothing an agent needs to call it correctly 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?

With 100% schema coverage and a single optional parameter, the schema already documents the `terms` array, case-insensitivity and the omit-for-full-glossary behavior. The description restates this rather than adding new meaning, so the baseline 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?

Specific verb plus resource ('look up official FIDES glossary definitions') and an explicit scope statement ('terminology used across the catalogs and filters'), with concrete examples of the term categories covered. An agent can distinguish this from the get_*/search_* entity siblings purely from the description.

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?

Gives a clear usage condition ('Use this for conceptual questions like ...') and explains both call modes (no args = full glossary, args = specific terms). It does not explicitly name when to prefer a sibling such as search instead, so it falls short of full when/when-not guidance.

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