Skip to main content
Glama

hub

by com.valksor
OverviewDiscussionsAdmin

dictionaries

Read-onlyIdempotent

Index of every Valksor dictionary reachable through this hub 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 dictionary by its id (the prefix before the first underscore). Each entry's host is that dictionary's public site, for reference only — you still reach its tools through this hub by their listed names, not via that host.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoRestrict the index to one dictionary by its id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dictionariesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds useful non-obvious behavior: the host field is for reference only and tools must still be called through this hub by their listed names.

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?

Three sentences, front-loaded with the resource and its contents, then the trigger, then the argument and host caveat. Dense but no sentence is filler.

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?

An output schema exists, so return-value explanation is not required, and the description still explains the shape of each entry (host) and how to act on the results. It fully equips an agent to call and use this tool.

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 the enum values and the description are fully documented in the schema, so the description adds no parameter detail beyond it. It does clarify the meaning of the id as 'the prefix before the first underscore', which is marginal added value. 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?

The description states a specific resource (an index of every Valksor dictionary reachable through the hub) and the exact content returned (current tool and prompt names). It is immediately distinguishable from every sibling, which are all language-prefixed research operations.

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 a clear trigger condition — call this to discover or re-check names, e.g. after an 'unknown tool'/'unknown prompt' error. It does not name alternative discovery paths, but for a hub index tool there is no real alternative to exclude.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources