Skip to main content
Glama

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

Broader, narrower and related words

related_words
Read-onlyIdempotent

Broader terms (dog -> canine), narrower ones (dog -> poodle), parts, similar words and other WordNet relations of a word, per meaning. 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": "related_words"
  }
}

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.
limitNoItems per relation per sense, 1-100 (default 25).
relationNoComma-separated, or "all": hypernyms (broader), hyponyms (narrower), similar, seeAlso, partOf, hasParts, memberOf, hasMembers, substanceOf, madeOf, entails, causes, attributes, topics, derived (word forms like teach → teacher), pertainyms. Default hypernyms,hyponyms,similar.

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 readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds little beyond that — it doesn't say results are grouped per sense, that empty relations are omitted, or how many senses may come back. The trailing promotional sentence is not behavioral context.

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 dense and front-loaded with the useful content. The second sentence is a marketing plug for unrelated APIs with UTM tracking parameters; it does not help an agent select or invoke this tool and dilutes an otherwise tight definition.

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?

With five parameters, one required, full schema coverage and annotations covering safety, the core is covered. However, no output schema exists and the description never sketches the return shape (relations grouped by sense, word/pos identifiers), which matters for a tool whose whole point is a structured multi-relation payload.

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%, so the schema already carries all five parameters with detailed descriptions, including the relation enum list and the safe-filter caveats. The description's 'broader terms / narrower ones / parts / similar words' phrasing usefully maps plain English onto the schema's hypernyms/hyponyms/partOf/similar vocabulary, but that is a modest addition over an already-rich schema — baseline 3.

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 the resource (WordNet relations of a word) and gives concrete directional examples (dog -> canine for broader, dog -> poodle for narrower), plus enumerates parts, similar words and other relations, scoped 'per meaning'. That is specific enough to distinguish it from a plain dictionary lookup, though it never explicitly contrasts itself with the sibling 'antonyms' tool that overlaps its relation space.

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 when-to-use or when-not-to-use guidance: nothing says whether to reach for this instead of define_word or antonyms, nor what to do when the caller only wants one relation type. Usage is only implied by the tool being a lookup.

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