Skip to main content
Glama
Sign In

Agent Data Tools: Web, documents and search

by io.github.Nutshell2000
OverviewDiscussionsAdmin

Dictionary definition: English words

dictionary
Read-only

Dictionary definition of an English word from Wiktionary, grouped by part of speech, with example sentences where Wiktionary gives them, plus the page link and the CC BY-SA attribution to show. Use for writing help, vocabulary, translation checks and word games. Example: word=serendipity. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "word": "<word>"
    },
    "name": "dictionary"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYesAn English word

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/open-world/non-idempotent, but the description adds real context on top: per-call pricing, 25 free calls, free failures, and the practical consequence that repeats cost money. It also surfaces the CC BY-SA attribution obligation, a behavioral constraint an agent must honor that appears nowhere in the structured fields.

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 what the tool returns, followed by usage, an example, then cost and safety notes — a sensible ordering with little filler. The clause 'Reads or computes only and changes nothing' restates readOnlyHint=true and is the one genuinely redundant sentence.

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?

There is no output schema, so the description correctly takes on the burden of describing the return shape (grouped by part of speech, examples, page link, attribution), and it also covers cost and billing behavior. An agent has everything needed to call this correctly and interpret the result.

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% with a single required 'word' parameter already documented in the schema. The inline example (word=serendipity) adds a small illustrative touch but no syntax or format guidance beyond what the schema provides, 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?

States a specific verb and resource: a dictionary definition of an English word sourced from Wiktionary. It further specifies the shape of the result (grouped by part of speech, example sentences, page link, attribution), which cleanly separates it from siblings like wikipedia or search that return prose or result lists.

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?

Names concrete use cases (writing help, vocabulary, translation checks, word games) so an agent knows when this is the right tool. It stops short of explicit exclusions or naming an alternative for cases like encyclopedic background, which would be needed for a 5.

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

All Agent Data Tools: Web, documents and search 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