7IT Solutions

Report a wrong or broken 7IT result

report_problem

Use this when a 7IT tool returned something that looks wrong, failed unexpectedly, or did not match what the user asked for, so 7IT can fix it. Sends a short report to 7IT: which tool, what went wrong, and optionally the site address involved. Do not include personal details or the conversation. Nothing changes for the user; it is only feedback.

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

Input Schema

Name	Required	Description
`url`	No	The site address the tool was used on, if any.
`tool`	Yes	The 7IT tool that misbehaved, for example "test_store_speed".
`problem`	Yes	What went wrong, in one or two sentences.

Output Schema

Name	Required	Description	Default
`received`	Yes	Whether the report was recorded

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds the crucial clarification that 'Nothing changes for the user; it is only feedback', reconciling the write-style hint with a harmless side effect, plus a privacy constraint on payload content. It stops short of describing submission behavior such as acknowledgement or rate limits.

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 tight sentences: trigger condition first, then payload contents, then the when-not and no-user-impact caveats. Every sentence carries information an agent needs before calling.

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 simple 3-parameter feedback tool with an output schema available to explain returns, the description covers trigger, payload, exclusions, and user impact completely. Nothing needed to call it correctly is missing.

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 100%, so the schema already documents all three parameters with examples and length limits. The description restates them at a high level ('which tool, what went wrong, and optionally the site address') without adding syntax or validation detail beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb-and-resource ('Sends a short report to 7IT') with the triggering condition spelled out (a tool returned something wrong, failed, or mismatched the request). It is clearly distinguishable from read-only siblings like test_store_speed or get_store_speed_index.

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?

Explicitly says when to use it ('when a 7IT tool returned something that looks wrong, failed unexpectedly, or did not match what the user asked for') and gives when-not constraints ('Do not include personal details or the conversation'). No alternative tool is named, but none is a real substitute for feedback submission.

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

All 7IT Solutions tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?