Skip to main content
Glama

Ask the Habidu coach

ask_coach
Destructive

Send a message to the user's Habidu AI coach and get its reply. Use it for advice, reflection, an overwhelming day, or a plan the user wants talked through; the coach knows their history and routines. For any direct change (add, move or delete a task, an inbox item or a routine) use the task / inbox / routine tools instead. Returns {ok:true, reply, suggestedReplies?, writes, tasksChanged}: the coach may still change the schedule when the user asks it to, and writes lists what it changed. The exchange also appears in the app's coach chat and counts toward the coach's daily limit. ok:false reasons: coach_limit, ai_consent_required, empty_message.

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": {
      "message": "<message>"
    },
    "name": "ask_coach"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe user's message to the coach, in their own words, e.g. "I have too much today, help me decide what to drop." Max 4000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description explains why: the coach 'may still change the schedule when the user asks it to' and `writes` lists what changed. It additionally discloses that the exchange appears in the app's coach chat and counts toward a daily limit, plus the ok:false reasons (coach_limit, ai_consent_required, empty_message) — context not recoverable from the annotations.

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?

Front-loaded with the action, then the routing rule, then return shape and failure modes; no filler sentences. It is compressed into a single dense paragraph, which makes the return-key enumeration slightly harder to scan, but every clause carries information.

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?

There is no output schema, so describing the return object and the ok:false reasons is necessary and present. Combined with the write side effect, the daily-limit note, and the sibling exclusion, an agent has everything needed to call this correctly and interpret the result.

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?

Only one parameter, and the schema already documents it fully (min/max length, an example message). The description adds no further meaning about the message field beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource: send a message to the Habidu AI coach and get its reply. It also draws a bright line against the task/inbox/routine tools, so an agent can distinguish it from siblings without opening any schema.

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?

Names concrete use cases (advice, reflection, an overwhelming day, a plan the user wants talked through) and an explicit exclusion: for any direct add/move/delete of a task, inbox item or routine, use the task/inbox/routine tools instead. When-to-use and when-not-to-use are both stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources