Skip to main content
Glama

Market Brew

See LLM Compression

analyze_content_summarizer

Use this when the user asks to run See LLM Compression. 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_content_summarizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior4/5

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

Annotations only flag non-read-only, open-world, non-idempotent; the description goes further by warning that the call may invoke external providers, consume quota, and populate caches, which is valuable cost/side-effect context an agent cannot infer from the schema. It also draws an explicit boundary ("Does not publish content or add opportunities to Launchpad"), consistent with destructiveHint=false, though idempotency/caching-reuse behavior across repeated identical calls is not addressed.

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?

At four sentences it is not bloated, and the side-effect warnings are packed efficiently. However, the lead sentence is wasted on a tautology and the useful information (quota, caches, non-publication) arrives after the agent has already been given a non-answer to "what does this do."

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 by far the richest nested schema in this family, the description omits essentially all input semantics and says nothing about the structured result shape beyond the word "analysis" (no output schema exists). The behavioral warnings are good, but an agent could not construct a valid, meaningful request from this description alone.

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 dozens of undocumented properties at 0% schema description coverage, and the description explains none of them. At best it obliquely gestures at three fields via "comparisons," "draft previews," and "generation," leaving crew, focus, snapshots, compressionLevel, and pagination entirely opaque.

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?

The first sentence is circular: "Use this when the user asks to run See LLM Compression" simply restates the title, so the actual operation (summarization/compression of content) is never stated. The second sentence adds partial substance by naming the outputs (structured analysis, comparisons, draft previews), but it does not differentiate this tool from the dense family of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The when-to-use clause delegates the decision back to the user ("when the user asks to run..."), which gives the agent no independent selection criterion. The only real conditional is "Request generation only when explicitly desired," and no alternative tool or exclusion (e.g., when to prefer analyze_content_depth or analyze_query_expansion) is named.

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