Skip to main content
Glama

list_mistakes

Read-onlyIdempotent

List journaled mistakes newest first with filters by label, problem tag, platform, specific problem, or recent days to review recurring errors and guide practice.

Instructions

Journaled mistakes, newest first, with the problem each was made on. Filter by label, problem tag, platform, one problem (platform and problem_id), or the last days days.

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": "list_mistakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
daysNo
kindNo
limitNo
platformNo
problem_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value with the 'newest first' ordering and the fact that each mistake is returned alongside its problem, but says nothing about the default result cap, pagination, or what happens when multiple filters are combined.

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 what the tool returns, then the filter modes in a single compact sentence with no filler. The only weakness is the ambiguous 'label' term, which costs a little precision without adding bulk.

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 values need not be described. For a 6-parameter tool with zero schema description coverage, though, the description leaves 'limit' undocumented and the label/kind mapping unclear, which are gaps an agent would hit when trying to bound results or filter by kind.

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 description coverage is 0%, so the description must carry all parameter meaning. It explains tag, platform, problem_id and days reasonably well, but leaves 'limit' (default 20, max 200) completely unmentioned and the word 'label' does not cleanly map to any parameter name — presumably 'kind' — leaving that mapping ambiguous.

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 resource (journaled mistakes) and an explicit ordering (newest first), plus the payload shape (each mistake's problem). It is clear what the tool returns, but it never distinguishes itself from siblings like mistake_kinds or mistake_patterns, which an agent could easily confuse with it.

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?

The description enumerates filter modes (label, problem tag, platform, single problem, recent days), which implicitly tells an agent how to narrow results. It gives no when-to-use guidance, no statement about when not to use it, and no pointer to the sibling tools that handle kinds or patterns.

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