Skip to main content
Glama

Market Brew

Separate Duplicate Keywords

analyze_keyword_separation

Use this when the user asks to run Separate Duplicate Keywords. Returns structured analysis and supported comparisons or draft previews for an API-key-enabled account. May invoke providers, consume quota and populate caches. Does not publish content or add opportunities to Launchpad. Request generation only when explicitly desired.

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": {
      "body": "<body>"
    },
    "name": "analyze_keyword_separation"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

The annotations only declare the safety envelope (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false); the description adds substantive cost and side-effect context beyond them, namely that it may invoke providers, consume quota, and populate caches. It also states what the tool will not do (no publishing, no Launchpad insertion), which is exactly the kind of boundary an agent needs before spending quota, and it does not contradict the annotations.

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?

Four short sentences, front-loaded with the trigger and followed by return shape, side effects, and boundaries; nothing is redundant filler. The opening sentence is wasted only because it restates the title, not because it is verbose.

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 quota-consuming, non-idempotent analysis tool with a heavily nested schema and no output schema, the description covers side effects and exclusions well but says almost nothing about the input body or what the analysis returns. An agent could invoke it safely but would be guessing at most of the body fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single body parameter is a deeply nested object with roughly two dozen properties and 0% schema description coverage, so the description carries the full explanatory burden and largely fails it. Only two fields are obliquely touched (generatePrompts via "Request generation only when explicitly desired", and comparison/draft content via "comparisons or draft previews"); query, topic, focus, pageSize, compressionLevel and the rest are left undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The operative sentence, "Use this when the user asks to run Separate Duplicate Keywords," is a verbatim restatement of the title, so it adds no meaning about what separation actually does. The follow-up sentence ("Returns structured analysis and supported comparisons or draft previews") describes the output shape rather than the operation and gives no differentiation from the many analyze_* siblings.

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?

There is a when-to-use clause, but it is circular: it tells the agent to invoke the tool when the user names the tool, which does not help selection among analyze_embedding_separation and the other siblings. It does supply real boundaries ("Does not publish content or add opportunities to Launchpad") and a caution ("Request generation only when explicitly desired"), which keeps this above a 2.

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