Skip to main content
Glama

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

Word family

word_family
Read-onlyIdempotent

Derived forms of a word grouped by part of speech (decide, decision, decisive, decisively). 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": "word_family"
  }
}

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.
depthNoLinks to follow, 1-3 (default 2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added behavioral value is the output shape (grouped by part of speech). It says nothing about how 'depth' links expand the answer or what the safe filter excludes — that lives only in the schema.

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 front-loaded, example-rich, and earns its place. The second sentence is a marketing link with UTM parameters that does nothing to help an agent select or invoke the 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?

For a read-only lookup with full schema coverage and no output schema, the description adequately conveys what comes back. What is missing is any signal about breadth or relationship to adjacent tools (define_word, antonyms), which is the main ambiguity an agent would face when choosing among them.

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 the four parameters including pos, safe, depth and the inflection note are already fully documented in the schema. The phrase 'grouped by part of speech' mildly echoes the pos filter but adds no syntax, defaults, or interaction detail beyond the schema. Baseline 3 is correct here.

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?

Names a specific resource and shape: 'Derived forms of a word grouped by part of speech', then makes it concrete with the decide/decision/decisive/decisively example. An agent knows exactly what this returns. It stops short of naming the sibling it is not (define_word, antonyms), so it earns 4 rather than 5.

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?

Usage is only implied by the example: an agent can infer 'use this when you want morphological relatives rather than a definition'. There is no explicit when-to-use, when-not-to-use, or routing to define_word/antonyms, so the agent must infer the boundary itself.

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