Skip to main content
Glama

report_problem

Read-only

Drafts bug reports or feature ideas in the maintainers' GitHub format, returns the text and a pre-filled link for the user to submit, and sends nothing automatically.

Instructions

Draft a bug report or idea for the project's GitHub repository in the maintainers' format. Sends nothing: it returns the text and a pre-filled GitHub link that the user opens and submits with their own account. Describe the technical problem only; never include seller names, message texts, contact data or listing links. Show the user the draft before giving them the link.

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": {
      "kind": "<kind>",
      "title": "<title>",
      "what_happened": "<what_happened>"
    },
    "name": "report_problem"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
toolNoBug: the MCP tool that failed
stepsNoBug: numbered steps to reproduce
titleYesOne line, English if possible
expectedNoBug: what should have happened. Idea: why it helps.
error_textNoBug: the error message, verbatim
what_happenedYesBug: what went wrong. Idea: what should exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

This is consistent with readOnlyHint=true and explicitly reassures the agent that it 'sends nothing', explaining exactly what comes back (the text and a pre-filled GitHub link) and that the user submits with their own account. That is meaningful behavioral context beyond the annotation, plus a privacy constraint a caller must respect.

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?

Four short sentences, front-loaded with purpose, then the no-side-effect guarantee, then the content restriction and the draft-first workflow. Each sentence adds a distinct, actionable constraint with no filler.

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 7-parameter tool with no output schema, the description covers both the return value and the submission flow, and it enforces the privacy boundary. Only minor gaps remain, such as the required minimums for title and what_happened, which the schema already handles.

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 86% and the schema already documents each field's meaning per kind (bug vs idea), so the baseline is 3. The description constrains content (technical problem only, no personal or listing data) but adds no per-parameter format or usage detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Draft') and resource ('bug report or idea') and adds the destination and format ('for the project's GitHub repository in the maintainers' format'), which separates it cleanly from drafting tools like draft_message or send_draft.

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?

It makes explicit when this applies (technical bugs or ideas about the project) and gives a hard exclusion: never include seller names, message texts, contact data or listing links. It also gives a workflow instruction (show the draft before giving the link), though it does not name a sibling alternative by name.

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