Skip to main content
Glama
Sign In
musterd

musterd

Official
by musterd-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

team_question

Ask a person or @team a question and end your turn; the answer arrives as your next turn, with optional one-line consequences for each choice.

Instructions

Ask a person a question (ADR 773), then end your turn: the answer arrives as your next turn. Not a question in chat. Options carry a one-line consequence.

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": {
      "to": "<to>",
      "text": "<text>"
    },
    "name": "team_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesa person, or '@team'
whyNo
textYes
anyoneNoany person may answer
optionsNo
blockingNoyou cannot go on without it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the single most important behavioral trait: this call ends the turn and the reply arrives asynchronously as the next turn. It does not cover what happens if no one answers, timeouts, or how '@team' delivery differs from a direct ask.

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 short sentences, front-loaded with the action and its turn-ending consequence; nothing is padded. The "(ADR 773)" reference is the one piece of noise that doesn't help an agent decide or call.

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?

For a 6-parameter, no-annotation, no-output-schema tool, the description covers the core interaction model but leaves gaps: what the returned answer looks like, what @team plus anyone does in combination, and the purpose of `why`. Adequate but not complete for the tool's complexity.

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 coverage is 50%; the description explains that "options" entries carry a one-line consequence, adding real meaning to the undocumented nested consequence field. However, `why`, `text`, and the interaction between `anyone` and `blocking` are left to the schema, and `why` is undocumented in both places.

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 concrete verb+resource ("Ask a person a question") and immediately delimits scope with "Not a question in chat," which separates it from chat-style siblings like team_send. The parenthetical "ADR 773" adds no meaning for an agent but doesn't obscure the purpose.

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 clear operational context: use it when you need an answer and are willing to yield ("then end your turn: the answer arrives as your next turn"). It also carves out a negative case ("Not a question in chat"), though it never names the alternative tool that would be used for a chat question.

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