Skip to main content
Glama

wiktionary_lookup

Read-onlyIdempotent

Retrieve word definitions from Wiktionary in multiple languages by providing the word and an optional language code.

Instructions

Look up a word definition in Wiktionary (multi-language).

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

Input Schema

NameRequiredDescriptionDefault
wordYesWord to look up
languageNoLanguage code (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that the lookup is multi-language, but it does not add further behavioral context such as rate limits, fallback behavior, or return shape.

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?

The definition is a single front-loaded sentence with no redundant or filler text. Every part of the sentence contributes to identifying the action and resource.

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 simple read-only lookup with fully documented parameters and clear annotations, the description is largely sufficient. It could say more about expected output or language behavior, but no major operational detail 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?

Schema description coverage is 100%, so both the word and language parameters are already documented in the schema. The description's "multi-language" phrase lightly reinforces the language parameter, but it does not add syntax or format guidance beyond the schema.

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 uses a specific verb and resource: "Look up a word definition in Wiktionary," and adds the scope "multi-language." It is clear what the tool does, but it does not explicitly distinguish itself from similar siblings such as dictionary_lookup or dictionary_lookup_language.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is for word-definition lookups and notes that Wiktionary is the source, but it gives no explicit when-to-use guidance, exclusions, or alternative tools to prefer for different dictionary or language needs.

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

Deploy Server

Other Tools