Skip to main content
Glama

askround_report

Retrieve the report for a stored question round or prompt set, defaulting to the latest, to inspect product mentions, rankings, rivals, claims, and cited pages.

Instructions

The report of a stored round or prompt set (default: the latest).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "askround_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundNoa round's or set's directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read operation by saying 'report,' but it does not disclose whether the report is generated or fetched, what permissions are needed, what happens if the round is missing, or what the output looks like.

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?

The definition is a single compact sentence with the default behavior front-loaded and no redundant wording. It is appropriately sized for a one-parameter tool.

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 low-complexity tool with one optional parameter and no output schema, the description covers the input default but says nothing about what the report contains or how it is returned. That leaves a meaningful gap around output expectations despite the simple interface.

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

Parameters4/5

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

Schema coverage is 100%, so the single optional 'round' parameter is already documented as a directory. The description adds useful meaning by stating that omitting it defaults to the latest round or prompt set, which is not in the schema.

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 description names a resource ('report') and its scope ('a stored round or prompt set') and notes the default, but it lacks a clear action verb such as retrieve or generate, so the agent must infer what operation is performed. It also does not distinguish itself from siblings like askround_run or askround_research.

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?

It does not state when to choose this tool over siblings or when not to use it; the only usage hint is the parenthetical default to the latest round or prompt set. Explicit alternatives or prerequisites are absent.

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