Skip to main content
Glama

mistake_patterns

Read-onlyIdempotent

Returns mistake counts grouped by label, problem tag, platform, and month over a selected period to reveal recurring coding-practice errors and guide revision.

Instructions

Mistake counts per label, broken down by problem tag, platform and month. Counts only; reading what they say about the user is up to you.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mistake_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault
kindsYes
by_tagYes
by_monthYes
by_platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: results are aggregates only, grouped across four dimensions, and no interpretive layer is applied. It does not disclose the default time window when `days` is omitted, which is the most consequential behavioral unknown.

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?

Two short sentences with the output shape front-loaded and the interpretation caveat second. The colloquial 'up to you' phrasing conveys a real constraint (no analysis layer), so it earns its place, though it could be stated more crisply.

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?

An output schema exists, so return structure need not be explained, and the grouping dimensions are covered. The missing piece is how the `days` window behaves by default, which an agent needs in order to call this correctly for a 'this month' vs 'all time' question.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter `days` has 0% schema description coverage and is never mentioned in the description, leaving its meaning (lookback window? day-of-month grouping?) and null default undefined. The mention of 'month' breakdown only loosely gestures at time scoping and does not compensate for the gap.

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?

The description states a specific resource (mistake counts) plus its aggregation dimensions (label, problem tag, platform, month), which clearly distinguishes it from list-style siblings. It stops short of naming which sibling to use for raw records, but the 'counts only' framing makes the aggregation role unambiguous.

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?

'Counts only; reading what they say about the user is up to you' implies the tool's role is aggregation, not inspection, which hints at when to pick it over list_mistakes or mistake_kinds. However, no alternative is named and no condition or prerequisite is stated, so the routing decision is left to inference.

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