Skip to main content
Glama

askround_run

Run all questions in a product file across AI providers to check whether a product is named, where it ranks, which rivals appear, and what claims and facts are returned.

Instructions

Ask every question of a product file (a prompt set) and return a brief per question: the runs naming the product and its best position per provider, its claims, the rivals, each fact with its answers' ids. detail: true returns every question's full report instead.

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": {
      "file": "<file>"
    },
    "name": "askround_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesthe product file (TOML); in this project: examples/askround.toml (3 questions), examples/modelado.toml (4 questions)
runsNo
detailNoevery question's full report
extractNo
max_costNorefuse, before any call, a run estimated above this (USD)
providersNoonly these providers (default: every one with a key)
backgroundNostart it as a job and return at once; read it with askround_job

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral load. It does disclose the return payload per question (runs, best position per provider, claims, rivals, facts with answer ids) and the effect of detail: true, which is real added value given there is no output schema. But it omits that this makes external provider calls that cost money (the max_cost/background parameters in the schema hint at charges and jobs), and it says nothing about rate limits or what happens when a provider key is missing.

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?

Two sentences, front-loaded with the action and then the return contract, with no filler. The middle enumeration ("the runs naming the product and its best position per provider") is compressed to the point of being hard to parse, which costs a point.

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 seven-parameter, no-output-schema, no-annotation tool, the description gives an adequate account of what comes back but leaves the mutation/cost profile and the job-mode workflow (background: true plus askround_job) unstated. An agent could call it, but could not confidently predict side effects or spend.

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 coverage is 71%, so several parameters are already documented in the schema (file, detail, max_cost, providers, background). The description adds meaning only for detail ("full report instead" vs the brief) and partially for the file parameter by describing what a prompt set yields. It adds nothing for runs, extract, or the interaction between background and askround_job.

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 states a specific action ("ask every question of a product file") plus the return shape, so the resource and verb are identifiable. However, jargon like "product file," "best position per provider," "claims," and "rivals" is undefined, and nothing distinguishes this batch runner from the sibling askround_ask for a single question.

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?

There is no explicit when-to-use or when-not-to-use guidance, nor any pointer to alternatives such as askround_ask for a single prompt or askround_job for retrieving background runs. Usage is only inferable from the phrase "ask every question of a product file."

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