Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Define a word

define_word
Read-onlyIdempotent

Definitions of an English word with example sentences, part of speech, pronunciation and inflections. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
posNoOnly this part of speech: noun, verb, adjective or adverb.
safeNoBest-effort family-friendly filter (default false). Drops senses WordNet tags as vulgar, derogatory, slur or slang, senses whose definitions describe sexual, excretory or illegal-drug meanings, and a list of profane and slur words, everywhere in the answer. Not a guarantee;
wordYesA word or phrase (up to 64 characters; "ice cream", "run away"). Inflected forms are matched to their base form: ran → run, mice → mouse, dogs → dog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered without prose. The description adds value by disclosing the shape of the answer (examples, POS, pronunciation, inflections), but says nothing about behavior on unknown words, empty results, or rate/lookup limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loaded with the useful content. The second sentence is pure promotional boilerplate with UTM-tagged marketing links and contributes nothing to tool selection, which drags the score down.

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

Completeness3/5

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

For a simple lookup with a fully documented schema and no output schema, the description covers what a caller gets back. It omits edge-case behavior (word not found, partial matches, response envelope), leaving a modest gap for an agent deciding how to handle results.

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 the schema itself explains the word normalization ('ran → run'), the pos enum, and the safe filter. The description only echoes 'part of speech' and 'inflections' already documented in the schema, adding no new semantics. Baseline 3 applies when the schema carries the load.

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 names a specific resource ('Definitions of an English word') and enumerates the payload (example sentences, part of speech, pronunciation, inflections), so an agent knows exactly what it returns. It stops short of differentiating itself from lookalike siblings such as word_family or antonyms, which keeps it out of the top band.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus the related word tools (antonyms, word_family), no prerequisites, and no exclusions. Usage is only inferable from the phrase 'Definitions of an English word'.

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