Skip to main content
Glama

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

Antonyms by meaning

antonyms
Read-onlyIdempotent

Opposites of an English word, by meaning (direct and indirect antonyms). 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": "antonyms"
  }
}

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that by specifying the result contains both direct and indirect antonyms and that lookup is meaning-based, but with no output schema it omits return shape, ordering, and empty-result behavior.

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 core clause is well front-loaded and efficient, but the second sentence is a promotional link ('More APIs from FitzTopPicks...') that does nothing to help an agent select or call the tool and dilutes the 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 simple 3-parameter lookup with no output schema, the description should describe the returned structure; it only hints that direct and indirect antonyms come back. Combined with full schema coverage and read-only annotations nothing critical is missing, but the answer format remains underspecified.

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%, with pos enum and safe filter fully documented in the schema itself, so the baseline is 3. The description's 'English word' phrase only loosely reinforces the word parameter and adds no syntax or edge-case detail beyond what the schema already provides.

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 concrete resource and result type: 'Opposites of an English word, by meaning (direct and indirect antonyms)'. An agent can tell this returns antonyms rather than definitions, distinguishing it from define_word. It stops short of explicitly naming siblings or contrasting use cases, which keeps it from a 5.

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 guidance on when to use this versus define_word or other word tools, no prerequisites, and no notes on limits (e.g., English-only, unknown-word behavior). The purpose implies usage, but nothing is stated explicitly.

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