Skip to main content
Glama

kelpo_report_issue

Tell Kelpo what went wrong: a defect in a take (words not said, lips, hands, outfit or place changing), a price or charge you find wrong, an unclear or contradictory message, a render too slow or stuck, a documented feature refused, a doc that says otherwise. One item per problem, with the job ids and shot, what you observed (quote values, messages, heard words) and what you expected. Send one report when the problems are known (e.g. after delivery), not one per call. Free; the Kelpo team reads every report (no automatic analysis; kelpo_get_report shows its status). Never promise the person a refund or a fix. Arguments: {"body": {"summary": "", "language": "fr", "items": [{"kind": "speech", "title": "", "observed": "<what happened, quoted>", "expected": "", "job_ids": [""]}]}}

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": {
      "body": "<body>"
    },
    "name": "kelpo_report_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), it discloses cost ('Free'), the no-automation/human-review model ('the Kelpo team reads every report (no automatic analysis)'), and where status surfaces (kelpo_get_report). It also warns implicitly against duplicate filings, which aligns with idempotentHint=false. No contradictions with the declared hints.

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?

Purpose is front-loaded in the first sentence and the operational rules follow in a logical order. The tail-end JSON example largely restates the schema the agent already holds, which is the one piece of real redundancy, and 'one item per problem' / 'not one per call' slightly overlap.

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 nested, mutation-style reporting tool with no output schema, the description supplies everything needed to call it correctly: granularity, required evidence style, batching policy, cost, review process, and where to check status. Limits (max 20 items, field lengths) are carried by the schema, so nothing critical is missing.

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?

Top-level schema coverage is 0% and the payload is a single nested 'body' object, so the description must compensate — and it does, spelling out that each item carries job ids and shot, quoted observations, and expectations, plus an inline example body. Gaps remain: the enum kinds 'montage', 'suggestion', 'other' and fields like 'assistant' and 'project_id' are never explained, so an agent must guess which kind to pick for edge cases.

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?

Starts with a specific verb and target ('Tell Kelpo what went wrong') and enumerates the exact problem classes it covers (take defects, pricing, slow renders, docs contradicting behaviour). It also names the read-side sibling (kelpo_get_report) so an agent can distinguish filing from checking status without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance: 'Send one report when the problems are known (e.g. after delivery), not one per call' — batching is stated as a rule, not left to inference. It also routes follow-up to kelpo_get_report and adds a conduct constraint ('Never promise the person a refund or a fix'), which removes a real failure mode absent from any structured field.

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