Skip to main content
Glama

Market Brew

Preview Spotlight Focus

analyze_spotlight_focus

Use this when the user asks to run Preview Spotlight Focus. 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_focus"
  }
}

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?

The description adds meaningful behavioral context beyond the annotations: it may invoke providers, consume quota, populate caches, and does not publish content or add opportunities to Launchpad. It also clarifies that generation should be requested only when explicitly desired. These are useful side-effect and safety details for a non-read-only, open-world tool.

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 front-loads the usage sentence, but that first sentence is largely wasted because it merely restates the tool name. The later sentences carry the useful behavioral information, so the structure is adequate but not efficient.

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?

Given the complex nested schema, lack of output schema, and non-read-only annotations, the description is incomplete. It covers side effects and publishing boundaries but omits the tool's actual analytical purpose and any parameter meaning, leaving significant gaps for correct invocation.

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 description does not explain any of the nested body parameters such as focus, query, topic, prompts, or generation flags. For a tool with a complex nested input object, this leaves the agent with no semantic guidance beyond the raw schema.

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 description largely restates the tool name and title: "Use this when the user asks to run Preview Spotlight Focus." It adds only a vague outcome, "structured analysis and supported comparisons or draft previews," without explaining what Spotlight Focus analysis actually does or how it differs from siblings like analyze_semantic_focus or analyze_spotlight_author.

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 only usage guidance is tautological: use it when the user asks to run it. The note "Request generation only when explicitly desired" gives one constraint for generation, but there is no guidance on when to choose this tool over alternatives or what prerequisites apply beyond an API-key-enabled account.

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