Skip to main content
Glama

askround_diff

Compare two runs of the same questions to see changes in answer share and rank, rivals, cited pages, and claims.

Instructions

What changed between two runs of the same questions (default: the latest two): share and rank, rivals, cited pages, claims.

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_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
newNo
oldNo
productNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the default selection behavior and the dimensions of the comparison output, which is more than the structured fields provide. It does not state that the operation is read-only, what happens when fewer than two runs exist, or how large a diff may be returned.

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?

A single front-loaded sentence with no filler; the core operation and the default come first. The trailing colon list of output dimensions is terse to the point of being slightly telegraphic, but it earns its space.

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?

For a tool with three 0%-documented parameters, no annotations, and no output schema, one sentence is thin: the agent cannot tell what values to pass for new/old/product or what constraints apply. The description defines the purpose but not enough to invoke it confidently beyond the no-argument default.

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%, so all three parameters (new, old, product) are undocumented in structured form. The description only implies that new/old are run selectors defaulting to the latest two; the product parameter is never mentioned, and the identifier format (ID, name, timestamp) is left entirely unclear.

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?

States a specific operation (diffing) on a specific resource (two runs of the same questions), and names the comparison axes (share/rank, rivals, cited pages, claims). It is distinguishable from siblings like askround_run or askround_report, though it does not explicitly name which sibling to use instead for a non-diff view.

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

Usage Guidelines3/5

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

The parenthetical '(default: the latest two)' tells the agent the tool works without arguments and which runs it will pick, which is genuine usage context. There is no explicit when-to-use or when-not-to-use guidance, and no statement of prerequisites (e.g. that at least two prior runs must exist).

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