Skip to main content
Glama
Sign In

CueScout

by io.github.telman03
OverviewDiscussionsAdmin

Show the latest AI answers to one tracked prompt

get_prompt_answers
Read-only

Use this when someone wants to read what the AI engines actually answered to one of their tracked prompts. Returns the most recent answer from each engine, whether the brand was named or cited, which brands were named, and the pages each answer cited.

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": {
      "prompt_id": "<prompt_id>"
    },
    "name": "get_prompt_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoWhich brand, by name or id, when the account tracks more than one. Leave empty to use the only brand; list_brands shows them all.
prompt_idYesThe prompt id, from list_prompts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare it a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description adds real substance: it returns the most recent answer per engine, brand-mention/citation flags, named brands, and cited pages. It omits freshness/pagination limits and error behavior, keeping it out of 5 territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the usage trigger front-loaded and the return contents following. Every clause carries information an agent can act on.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the return shape (per-engine answers, brand naming/citation status, cited pages), which is the key gap a caller would otherwise face. Only minor omissions remain, such as how fresh 'most recent' is and what happens when no answers exist yet.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both prompt_id and brand are already documented in the schema (including the 'leave empty to use the only brand' fallback and the list_brands pointer). The description adds nothing beyond the schema, making the baseline 3 correct.

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

Purpose5/5

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

States a specific verb (read/show) and resource (the AI answers for one tracked prompt), and the title reinforces the scope as 'latest'. It is distinguishable from the aggregate-oriented siblings like get_ai_visibility and get_profile without opening the schema.

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?

'Use this when someone wants to read what the AI engines actually answered' is an explicit trigger condition, and 'one of their tracked prompts' implies the list_prompts prerequisite. It stops short of naming an alternative or an exclusion, so it is not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CueScout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources