Skip to main content
Glama

ask

Read-only

Answers open questions from retrieved app-store reviews and patch notes, citing review IDs and versions to link complaints to specific game releases.

Instructions

Answer an open question (e.g. "when did matchmaking complaints start?") from retrieved reviews and patch notes, citing review ids and versions. Calls Claude Sonnet: costs about $0.014 per question, so prefer the other tools first.

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": {
      "app": "<app>",
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesGame slug, e.g. critical-strike.
questionYesA question about the reviews.

Output Schema

NameRequiredDescriptionDefault
notesYes
answerYes
cost_usdYes
cited_versionsYes
cited_review_idsYes
removed_citationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real value beyond them by disclosing that this invokes Claude Sonnet, quotes a per-question cost (~$0.014), and states that answers cite review ids and versions. Latency or answer-length behavior is not mentioned, keeping it below 5.

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?

Three tight sentences: what it answers, how it answers (with citations), then the cost caveat. The cost warning is deliberately placed last as the decision-relevant constraint, and no sentence is filler.

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 annotations covering the read-only/open-world profile and an output schema covering the return shape, the description only needed to justify existence, cost, and citation behavior—all present. A note on answer latency or when the model may lack evidence would make it fully complete.

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 parameters are already documented (game slug, question about reviews) and the baseline of 3 applies. The description's example question and the mention of reviews/patch notes add only marginal meaning beyond the schema.

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 and resource ('answer an open question') and scopes it to reviews and patch notes with citation output. The example question plus 'open question' framing separates it from the structured siblings (search_reviews, top_issues, sentiment_trend) without needing to name them.

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?

Gives explicit when-not guidance via cost ('prefer the other tools first') and an illustrative example of the kind of open-ended question this is for. It stops short of naming a concrete alternative or a precise threshold for when the cost is justified, so it is a strong 4 rather than a 5.

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