Pressure Atlas

Close feedback

close_feedback

DestructiveIdempotent

Close feedback this account sent when the user says it is resolved or no longer wanted, so it stops showing as open. Closing is final: closed feedback cannot be changed or reopened, and raising it again means sending new feedback. The team keeps it on record. Ask the user first. Does not count against the daily quota.

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": {
      "id": "<id>"
    },
    "name": "close_feedback"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The feedback id, as send_feedback and list_feedback return it.

Output Schema

Name	Required	Description	Default
`id`	Yes	The feedback id.
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds non-obvious behavior beyond them: closing is irreversible, closed items stay on record, the user must be consulted first, and the action does not consume the daily quota — the last detail is unavailable anywhere else.

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?

Front-loaded with the core action and the finality constraint, then the user-consultation caveat and quota note. All sentences carry information, though the quota sentence is a slight tail-end addendum rather than tightly integrated.

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?

With an output schema present, return values need no explanation, and the annotations cover safety semantics. What remains — irreversibility, record retention, user-consent requirement, quota immunity — is fully covered, so an agent has everything needed to call this correctly.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents that id is the feedback id as returned by send_feedback and list_feedback. The description adds no syntax, format, or sourcing detail beyond the schema, so the baseline of 3 applies.

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?

Specific verb (close) plus resource (feedback this account sent) and an explicit scope qualifier about when the user considers it resolved or unwanted. It also implicitly separates itself from edit_feedback by stating closing is final and feedback cannot be changed once closed.

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?

Gives the triggering condition ('when the user says it is resolved or no longer wanted'), a required precondition ('Ask the user first'), and names the alternative path for reopening ('raising it again means sending new feedback'), which routes the agent to send_feedback.

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

All Pressure Atlas 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?