Skip to main content
Glama
duckAsteroid

brindley

by duckAsteroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_question

Resolve open questions by label or match: delete them and record the decision, or mark them answered in place with a tick.

Instructions

Resolve an open question, named by its label (id, e.g. "Q3") or match. Default mode "remove": delete it and record the decision under its label in record_in (default "Decisions", e.g. "Agreed direction"). Mode "tick": keep it as "- [x] Q3 … — answer".

Input Schema

NameRequiredDescriptionDefault
idNoThe question's label, e.g. "Q3" (as `get`, `questions` and `next_question` report it).
refYesInitiative (ticket/issue): "collection#n" (e.g. "lgm#22"), a bare number, or a path.
modeNo
matchNo
answerYes
record_inNo
collectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • addedInput schema / properties / id
      Added value: +{
+  "description": "The question's label, e.g. \"Q3\" (as `get`, `questions` and `next_question` report it).",
+  "type": "string"
+}
    • removedInput schema / properties / index
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
  2. Changed1 schema field changedv2.6.0
    • changedInput schema / properties / ref / description
      Previous value: -"Initiative: \"collection#n\", a bare number, or a path."New value: +"Initiative (ticket/issue): \"collection#n\" (e.g. \"lgm#22\"), a bare number, or a path."
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose the key mutation semantics: default 'remove' deletes the question and records the decision under its label in record_in, while 'tick' keeps it as a checked entry. This transparency about destruction and persistence is strong, though permissions and return format are unstated.

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?

Dense and front-loaded, communicating the core action, mode split, and defaults in a few compact sentences. It is slightly cramped and has a stray quotation mark, but nearly every phrase earns its place.

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?

For a 7-parameter mutation tool with no annotations and no output schema, it covers the critical behavior (destructive default, where records go, mode alternative). Remaining gaps are the unexplained collection parameter and return-value behavior, but the essential calling contract is present.

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?

With only 29% schema coverage, the description compensates well by giving meaning to id (label e.g. 'Q3'), match, mode (with enum behavior and default 'remove'), record_in (default 'Decisions'), and answer (via the tick rendering). It leaves collection and ref semantics to the schema, so it adds substantial but not complete meaning.

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+resource: 'Resolve an open question,' and immediately clarifies the object ('an open question, named by its label or match'). This distinguishes it from siblings like add_question, split_question, and next_question, though it never names an alternative.

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

Usage Guidelines3/5

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

It usefully explains the two operating modes ('remove' default vs 'tick') and what each does, which guides mode selection. However, it gives no guidance on when to choose resolve_question over sibling tools like next_question or add_question, so usage is only implied by workflow context.

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

Deploy Server

Other Tools