Skip to main content
Glama

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

Synonyms by meaning

synonyms
Read-onlyIdempotent

Synonyms of an English word, grouped by meaning (each sense with its definition), so you pick the right sense. "safe" hides offensive words. 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": "synonyms"
  }
}

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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds that the response is sense-grouped with definitions and explains the safe filter's effect, which is real value; however, the safe explanation largely restates the schema field description, and there is no disclosure of response size, sense ordering, or fallback behavior when a word is unknown.

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?

The core sentence leads with the resource and its key structural trait, and the safe note follows logically. The trailing promotional blurb with UTM tracking is unrelated to tool selection 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 no output schema, the description must carry the return-value burden; it does say results are grouped by meaning with per-sense definitions, which is the essential shape. It still omits what a sense entry concretely contains (word lists per sense), behavior for no-match input, and any note on result size, leaving gaps for a tool whose output is undocumented elsewhere.

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 word (including base-form matching), pos, and safe are already fully documented. The description reinforces safe as 'hides offensive words' but adds no syntax or format detail beyond the schema, so it sits at the baseline.

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?

States a specific resource (synonyms of an English word) and a distinguishing structural trait: results are grouped by meaning, each sense with its own definition. That differentiates it from a plain thesaurus or from siblings like antonyms or define_word, though no sibling is named explicitly.

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 phrase 'so you pick the right sense' implies the intended use (disambiguating a word's meanings), and the safe flag is given a use case (hiding offensive words). There is no explicit when-to-use versus alternatives guidance and no statement of when not to use it, such as for definitions or opposites.

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