Skip to main content
Glama

dictionaries

Read-onlyIdempotent

Index of every Valksor server reachable through this hub — the dictionaries, margrave (id margrave) and the Paņem brīvdienu calendar (id latvia) — and its CURRENT tool and prompt names (each named _). Call this to discover or re-check names — e.g. after an 'unknown tool'/'unknown prompt' error. The optional language argument narrows the result to one server by its id (the prefix before the first underscore). Each entry's host is that server's public site, for reference only — you still reach its tools through this hub by their listed names, not via that host.

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

Input Schema

NameRequiredDescriptionDefault
languageNoRestrict the index to one server by its id.

Output Schema

NameRequiredDescriptionDefault
dictionariesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Restrict the index to one dictionary by its id."New value: +"Restrict the index to one server by its id."
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "livonian",
      -  "latin",
      -  "slavonic",
      -  "scythian",
      -  "norse",
      -  "latgalian",
      -  "anglo",
      -  "interslavic"
      -]New value: +[
      +  "livonian",
      +  "latin",
      +  "slavonic",
      +  "scythian",
      +  "norse",
      +  "latgalian",
      +  "anglo",
      +  "interslavic",
      +  "margrave",
      +  "latvia"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "livonian",
      -  "latin",
      -  "slavonic",
      -  "scythian",
      -  "norse",
      -  "latgalian"
      -]New value: +[
      +  "livonian",
      +  "latin",
      +  "slavonic",
      +  "scythian",
      +  "norse",
      +  "latgalian",
      +  "anglo",
      +  "interslavic"
      +]
  3. Added

TDQS

A4.4/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 safety is covered. The description adds non-obvious behavior beyond that: the index reflects CURRENT names (it is a live registry that can change), and the `host` field is not an alternate invocation route — an agent could otherwise wrongly try to reach a server directly.

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?

The most important information (what it indexes, what the ids mean) is front-loaded, and the error-trigger guidance follows immediately. It is dense but single-paragraph and readable; the host caveat is stated twice in slightly different words ('for reference only' and 'not via that host'), which is the only clear redundancy.

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?

An output schema exists, so return values need not be enumerated, yet the description still explains the useful fields (`host`) and the naming convention within entries. For a single-optional-parameter, read-only discovery tool this covers everything an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum is documented, so the baseline would be 3, but the description adds real meaning: the `language` argument filters by server id and that id is the prefix before the first underscore, which explains why values like 'margrave' and 'latvia' appear in a parameter named language. It does not clarify how prompt names differ from tool names in the result.

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 states a specific verb and resource: an index of every server reachable through the hub and its current tool/prompt names, with each name following the <id>_<verb> convention. This cleanly separates it from every sibling tool, which are concrete language/calendar operations rather than a registry lookup.

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?

It gives an explicit trigger — 'Call this to discover or re-check names — e.g. after an 'unknown tool'/'unknown prompt' error' — which is exactly the decision point an agent needs. It also warns that servers' `host` values are informational and tools are still invoked through the hub, preventing a likely misuse; it stops short of saying when not to call it (e.g. avoid calling pre-emptively every turn).

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