Skip to main content
Glama

Confirm or ignore a suggested blocker

standcast_decide_suggestion
Idempotent

Records a person's confirmed or ignored answer to a suggested blocker in their standup draft, capturing their decision without choosing for them.

Instructions

Records the person's answer to a suggested blocker from their own draft. Call it only after asking the person whether the suggestion is a real blocker. Use decision ignored when they say no. When they say yes, add it to the blockers in their own words with its ref; submitting the daily confirms it, and decision confirmed records the answer right away. Calling with decision confirmed is optional, because submitting a daily with a blocker that carries the suggestion's ref confirms it. Never decide on the person's behalf.

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": {
      "id": "<id>",
      "decision": "<decision>"
    },
    "name": "standcast_decide_suggestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSuggestion id from the draft.
orgNoOrganization login. Optional when the person belongs to a single organization.
decisionYesconfirmed when the person said it is a real blocker, ignored when not.

Output Schema

NameRequiredDescriptionDefault
idYes
decisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only declare idempotent and non-destructive), the description discloses a non-obvious behavioral interaction: submitting a daily with a blocker carrying the suggestion's ref implicitly confirms the suggestion, making an explicit 'confirmed' call redundant. It also states the consent constraint ('Never decide on the person's behalf'), which is a behavioral rule no structured field conveys.

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?

Purpose is front-loaded in the first sentence and the workflow follows logically. The clause 'Calling with decision confirmed is optional, because submitting a daily with a blocker that carries the suggestion's ref confirms it' partially repeats the preceding sentence, costing a little tightness in an otherwise efficient paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering the safety profile and an output schema covering return values, the description supplies exactly the missing pieces: the consent precondition, the two decision branches, and the interaction with standcast_submit_daily. An agent has everything needed to call this correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains that the id is a 'ref' that must be carried onto the blocker when the person says yes, tying the parameter to the submit_daily confirmation path. The decision values are already documented in the schema enum, so that part is restated rather than added.

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?

The description opens with a specific verb and resource: 'Records the person's answer to a suggested blocker from their own draft.' This distinguishes it clearly from sibling tools such as standcast_submit_daily and standcast_list_blockers, since the object is a suggestion tied to the caller's draft, not the daily itself.

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 an explicit precondition ('Call it only after asking the person'), maps each enum value to a real-world condition ('Use decision ignored when they say no'), and names the alternative path — adding the blocker with its ref and letting submission confirm it. It even flags that calling with 'confirmed' is optional, which is exactly the when-not guidance an agent needs.

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