Skip to main content
Glama

Market Brew

Test New Entity Coverage

analyze_spotlight_author

Use this when the user asks to run Test New Entity Coverage. 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_spotlight_author"
  }
}

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?

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds real context beyond them: it warns that the call may invoke providers, consume quota, and populate caches, and it explicitly bounds the blast radius by stating it does not publish content or add opportunities to Launchpad. That side-effect and quota disclosure is exactly the kind of information annotations cannot convey. It stops short of saying whether results are cached/reusable or how long an invocation takes, which keeps it out of the top band.

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 description is short and mostly front-loaded, with the safety-relevant constraint (no publishing, no Launchpad writes) placed reasonably early. However, the first sentence is wasted boilerplate that duplicates the title, and the phrases "structured analysis and supported comparisons or draft previews" are vague hedges that convey little.

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?

This is a complex, deeply nested request object with no output schema and zero parameter documentation, so the description carries the full burden — and it does not deliver. It never explains the shape of the body, what "focus" anchors/entities do, how comparison URLs are used, or what the returned "comparisons" and "draft previews" actually contain. Only the quota/cache/publishing caveats are genuinely complete.

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 top-level body parameter nests dozens of undocumented properties (crew, focus.anchors, content, comparisonUrl, generatePrompts, pageSize, compressionLevel, and more). The description adds no meaning for any of them and never mentions the body wrapper, the required crew.id, or the generatePrompts/recommendations flags it implicitly gestures at with "Request generation only when explicitly desired."

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 opening sentence, "Use this when the user asks to run Test New Entity Coverage," simply restates the title rather than describing what the tool does, and the tool name (analyze_spotlight_author) does not match the title, leaving the actual operation ambiguous. Only the fragment "Returns structured analysis and supported comparisons or draft previews" hints at output, and it never says what is being analyzed or how this differs from siblings like analyze_spotlight_focus or analyze_query_coverage.

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?

"Use this when the user asks to run Test New Entity Coverage" is circular — it gives no real trigger condition an agent could recognize in a user request. The one genuine constraint, "Request generation only when explicitly desired," is a useful gating rule but is not tied to any named parameter or alternative tool, and no sibling is ever mentioned as the choice to make instead.

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