Skip to main content
Glama

Market Brew

Fan Out Embeddings

analyze_ai_mode

Use this when the user asks to run Fan Out 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_ai_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the tool may invoke providers, consume quota, and populate caches, and that it will not publish content or add opportunities to Launchpad. These details are consistent with readOnlyHint=false and destructiveHint=false and give an agent real cost and side-effect awareness. It stops short of describing rate limits, latency, or failure behavior.

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 definition is short, front-loaded with the trigger, and each sentence carries a distinct point about output, side effects, exclusions, and generation scope. Minor redundancy exists in restating the tool name as the usage condition, but nothing is bloated.

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 tool with a deeply nested request body, 0% schema description coverage, and no output schema, the description leaves the agent without parameter guidance or clear differentiation from sibling analyses. It covers cost and scope well but is not complete enough to invoke the tool confidently without inspecting the schema.

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?

Schema description coverage is 0% and the single body parameter contains a large nested object with many undocumented fields such as focus, prompts, compressionLevel, and rankingSensorId. The description adds essentially no field-level meaning, only a faint hint that generation-related options should be used deliberately. It does not compensate for the coverage gap.

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

Purpose3/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 Fan Out Embeddings" largely restates the title, and the description never explains what Fan Out Embeddings actually computes. It does add that the tool returns structured analysis plus comparisons or draft previews, which gives some sense of the output, but it does not distinguish this from the closely named sibling analyze_vector_fanout.

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 trigger is stated only circularly (use it when the user asks for this tool), and no alternative sibling is named for overlapping analyses. It does provide one real usage constraint, "Request generation only when explicitly desired," and clarifies the tool will not publish content or add to Launchpad, which helps bound expectations.

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