streak_statusRetrieve the current and longest streak for a goal, measured in days met, to track progress and consistency.
Current and longest streak for a goal (streaks measured in days met).
| Name | Required | Description | Default |
|---|---|---|---|
| goal_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral load; 'status' implies a read, and the parenthetical clarifies the measurement unit (days met), which helps interpret the result. It still omits failure behavior (e.g., missing goal) or any permission/pagination context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence that front-loads what the tool returns. Efficient, though the parenthetical definition could be folded in slightly more cleanly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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. However, for a tool sitting among get_progress, history, and list_goals, the definition gives no routing signal about when this is the right one to call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter goal_id has 0% schema description coverage, and the description only obliquely refers to 'a goal'. It does not clarify whether the id is an internal integer reference, how to obtain it, or what happens with an invalid id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific resource (streak) and its scope (current and longest) for a goal, which is clear enough to act on. It does not explicitly distinguish itself from siblings like get_progress or history, so it falls short of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance and no mention of alternatives such as get_progress or history. The agent must infer the context entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.