Skip to main content
Glama

decide_assumption

Record whether a person kept, overturned, or reopened an assumption, with their own words required when overturning. Capture assumption decisions accurately.

Instructions

Record what the person said about an assumption (A3): state kept or overturned (or open again), words the person's own words, required when overturned. Only the orchestrator, or the person's own session, may. Answering a batch on the desk does this for you.

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": {
      "assumption": "<assumption>",
      "state": "<state>"
    },
    "name": "decide_assumption"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
wordsNo
projectNo
assumptionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/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 disclosure burden. It does add real behavioral context — the authorization constraint and the conditional rule that `words` is required when the assumption is overturned — but it never states the side effects (does it mutate the assumption's lifecycle record?), idempotency, or that it is a write operation beyond the verb 'Record'.

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?

Three dense sentences with the core action and required state values front-loaded, and no filler. The telegraphic phrasing and unexplained 'A3' shorthand cost a little clarity but nothing is wasted.

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?

An output schema exists, so return values need not be described, and the auth plus overturn-requirement details are covered. However, for a 4-parameter tool with zero schema documentation and zero annotations, leaving `project` and `assumption` undefined and the mutation's effects unstated is a meaningful gap.

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 0%, so the description must compensate and only partly does. It defines the allowed `state` values and explains `words` as the person's own words with its conditional requirement, but `project` and `assumption` are left entirely unexplained — no format, identifier, or reference semantics for either.

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 verb and resource: 'Record what the person said about an assumption', and enumerates the decision states (kept, overturned, open again). The purpose is identifiable, but domain shorthand ('A3') and terms like 'orchestrator' assume insider knowledge, and it does not clearly separate itself from the sibling `assume`.

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?

Provides an explicit permission gate ('Only the orchestrator, or the person's own session, may') and an explicit exclusion: if you are answering a batch on the desk, that path already does this. What is missing is a positive statement of when to prefer this over `assume` or `desk_answer` beyond the batch case.

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