Skip to main content
Glama

Market Brew

Add Spotlight opportunities to Launchpad

add_spotlight_visualizer_to_launchpad

Use this when the user explicitly asks to add Spotlight Bridge opportunities to Launchpad. Identify the destination Crew, licensed website, source analysis, and selected entities first. This persists opportunities. Repeated additions can increment detection counts. Do not retry successful entries after a partial failure.

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": "add_spotlight_visualizer_to_launchpad"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the call persists opportunities, that repeated additions can increment detection counts (explaining the non-idempotent hint concretely), and that partial failures should not be retried for already-successful entries. That retry-safety note is exactly the kind of context annotations cannot convey; it stops short of stating permission or licensing requirements beyond the prerequisite mention.

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 trigger condition is front-loaded, followed by prerequisites and then operational caveats, in five dense sentences with no filler. Structure is logical and easy to scan.

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

Completeness3/5

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

For a non-idempotent, open-world write tool with a large nested schema and no output schema, the description covers trigger, prerequisites, side effects, and failure handling well. It omits what a successful response looks like and any licensing or permission constraints implied by 'licensed website', leaving gaps for a mutation of this complexity.

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% on a single deeply nested body object with dozens of fields (focus anchors/entities, pageSize, compressionLevel, snapshotId, and more). The description names four concepts that map loosely to top-level fields (crew, website, analysis, entities), but most nested parameters remain unexplained in both schema and prose, so it only partially compensates.

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

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (add Spotlight Bridge opportunities to Launchpad) and the title reinforces it. It does not explicitly distinguish itself from the sibling add_spotlight_author_to_launchpad, so an agent must infer the 'visualizer' vs 'author' split from the tool name rather than the prose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states a clear activation condition (the user explicitly asks) and lists prerequisites to resolve first: destination Crew, licensed website, source analysis, and selected entities. It does not name an alternative tool or spell out when not to use it, but the explicit-ask gate and prerequisite list give solid routing guidance.

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