Skip to main content
Glama

Report a problem to Cuttr AI

report_problem

Sends a problem to the Cuttr AI team, who reply by email. Include the exact error text and the step that failed. Never include API keys, passwords or tokens.

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": {
      "summary": "<summary>"
    },
    "name": "report_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
stepNoWhich step of the skill failed
errorNoThe exact error text
run_idNoThe run_id given at the end of the editor's instructions, if any
systemNoOS, tool (Claude Code, Codex, Claude app) and versions
summaryYesOne line: what went wrong

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses that a human team reads the report and replies asynchronously by email, and it adds a hard security constraint against including API keys, passwords, or tokens. It does not say what the tool returns on success (confirmation, ticket id) or whether submissions are rate limited, so it falls short of a 5.

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?

Three short sentences with no waste: what it does first, then what to include, then the safety prohibition. Every sentence earns its place and the ordering is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, one-required tool with no annotations and no output schema, the description covers purpose, required content, and the critical safety rule. The main remaining gap is the return behavior after submission, which the absence of an output schema leaves undocumented.

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 coverage is 83%, so the schema already explains slug, step, error, run_id, system, and summary. The description only reinforces the error and step fields and adds no format, length, or content guidance beyond them. Baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a concrete verb and destination: it sends a problem report to the Cuttr AI team. The scope is understandable without opening the schema, and no sibling tool overlaps with it. It stops short of saying what kinds of problems are in scope (skill setup failures, per the parameters), which keeps it from a 5.

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?

Usage is only implied: 'Include the exact error text and the step that failed' tells the agent how to fill the report but not when to file one versus troubleshooting another way. There is no explicit when-to-use or when-not-to-use statement, though the sibling set contains no comparable alternative to route to.

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