Skip to main content
Glama

Market Brew

Separate Duplicate Embeddings

analyze_embedding_separation

Use this when the user asks to run Separate Duplicate Embeddings. 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_embedding_separation"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real operational cost: it may invoke external providers, consume quota, and populate caches, which is important for a non-idempotent, open-world tool. It also draws negative scope boundaries (does not publish content or add to Launchpad), usefully clarifying what the mutation does not do even though destructiveHint is false.

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?

Four short sentences, reasonably front-loaded with the usage cue before the behavioral notes. However, the lead sentence is wasted on a restatement of the title, so a meaningful share of the text does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-complexity tool with a deep nested schema, no output schema, and 0% parameter documentation, the description covers only side effects and publishing exclusions. It leaves the actual analysis semantics and every input field undocumented, so an agent cannot reliably construct a correct call from this definition.

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

Parameters1/5

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

Schema description coverage is 0% and the single body parameter expands into roughly 25 nested fields (query, topic, content, includeVectors, compressionLevel, pageSize, etc.), none of which the description mentions. With zero compensating text, an agent must guess the meaning and required combinations of nearly every field.

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?

"Use this when the user asks to run Separate Duplicate Embeddings" simply restates the title and tool name. The only added substance is the generic phrase "returns structured analysis and supported comparisons or draft previews," which does not explain what separating duplicate embeddings actually computes or how it differs from vector-oriented siblings like analyze_vector_fanout or analyze_heading_vector_similarity.

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?

The stated trigger is circular (use it when the user asks for it), giving no real condition for selecting this tool over the many other analyze_* tools. The one concrete constraint, "Request generation only when explicitly desired," implies a generation flag but never names a parameter or explains when/when not to enable it.

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