Skip to main content
Glama

mistake_kinds

Read-onlyIdempotent

List existing mistake labels, most frequent first, so you can reuse them when logging new mistakes and keep similar errors counted together.

Instructions

Every mistake label used so far, most frequent first. Reuse these labels when logging new mistakes so the same kind of mistake is counted together.

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_kinds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world operation, so the description's job is to add content context, which it does by disclosing that results are the vocabulary of labels accumulated over time and sorted by frequency. It does not say whether counts are returned or how many labels come back, though the output schema likely covers that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste: the first front-loads what is returned and how it is ordered, the second explains the downstream use. Nothing could be cut without losing 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?

For a zero-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs to decide to call it and how to use the result. No prerequisites, auth concerns, or side effects are plausible here.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema coverage figure is moot with an empty properties object.

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 names a specific resource (every mistake label used so far) and its ordering (most frequent first), which is enough to distinguish it from list_mistakes and mistake_patterns in practice. It stops short of naming those siblings explicitly, so an agent must infer the boundary.

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?

"Reuse these labels when logging new mistakes so the same kind of mistake is counted together" gives clear, actionable context for what to do with the results, effectively routing the agent to call this before logging. It offers no explicit exclusion or contrast with the sibling list_mistakes tool.

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