Skip to main content
Glama

assume

Log an assumption—unanswered question, chosen option, rationale, affected tickets/people—so work continues and the orchestrator can confirm it later; returns a reference number.

Instructions

Record an assumption you made so the work does not block: the question the plan did not answer, the choice you made, why, the tickets it touches (T3, ...), and who it affects. Returns its number (A1, A2, ...): tell the orchestrator that number in one line and carry on. The orchestrator confirms open assumptions with the person once per milestone. Never use this for what must go to the person directly (prod deploys, secrets, money, new contacts, deleting data).

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": {
      "question": "<question>",
      "choice": "<choice>",
      "why": "<why>"
    },
    "name": "assume"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyYes
choiceYes
affectsNo
projectNo
ticketsNo
questionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the whole burden and does well: it discloses that the call is non-blocking, that it returns a sequential identifier (A1, A2, ...), and that the orchestrator batches human confirmation once per milestone. It does not cover persistence, deduplication, or what happens if the same assumption is recorded twice, which is the main remaining gap for a write tool.

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 dense sentences: the first front-loads what to record and the field mapping, the second covers the return value, the follow-up action, and the hard exclusions. No sentence is filler and the escalation caveat is placed last where it is most likely to be read before acting.

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?

An output schema exists, so omitting return-value detail is fine, and the description still usefully names the A-number format. For a six-parameter mutation tool with no annotations, the only meaningful shortfall is the undocumented project parameter and the absence of any permission or side-effect note.

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 description coverage is 0% and the schema carries only bare titles, so the description must compensate and largely does — it defines question, choice, why, tickets and affects with concrete meaning. The sixth parameter, project, is never mentioned, leaving one field unexplained.

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?

The description opens with a specific verb+resource ("Record an assumption you made") and immediately scopes the intent ("so the work does not block"). It tells the agent exactly what artifact is produced, though it never names a sibling such as decide_assumption, so the split between recording and resolving an assumption is left implicit.

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

Usage Guidelines5/5

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

It gives a clear positive trigger (a question the plan did not answer, blocking would stall work), a follow-up procedure (tell the orchestrator the A-number in one line and carry on), and an explicit exclusion list covering prod deploys, secrets, money, new contacts and data deletion. An agent knows both when to call it and when to escalate to the person instead.

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