FogBugz

Close Case

close_case

Destructive

Mark a FogBugz case as resolved or will not fix, adding optional comments to document closure reasons.

Instructions

Closes a FogBugz case (marks it as will not fix / done). Example: close case 42 with comment "Closed — duplicate of case 10".

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": {
      "caseId": "<caseId>"
    },
    "name": "close_case"
  }
}

Input Schema

Name	Required	Description	Default
`caseId`	Yes	The ID of the case to close
`comment`	No	Comment to add when closing. Plain text only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.8Apr 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by describing a write operation that changes case status. The description adds context beyond annotations by specifying the closure status ('will not fix / done') and providing an example with a comment, though it lacks details on permissions or side effects.

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?

The description is front-loaded with the core action, followed by a concise example that illustrates usage. Both sentences are necessary and efficient, with no redundant information, making it easy to scan and understand quickly.

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?

Given the tool's complexity (destructive mutation with 2 parameters), annotations cover safety aspects, and schema fully describes inputs. The description adds useful context on closure status and an example, but lacks output details (no schema) and could clarify more on behavioral traits like error conditions.

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 100%, so the schema fully documents both parameters. The description adds minimal value by mentioning a comment example, but does not provide additional semantics or constraints beyond what the schema already states (e.g., caseId is numeric, comment is plain text).

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 clearly states the verb ('Closes') and resource ('a FogBugz case'), and specifies the action's effect ('marks it as will not fix / done'). It distinguishes from siblings like 'reopen_case' and 'resolve_case' by focusing on final closure with specific status implications.

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?

The description implies usage for final case closure (e.g., 'will not fix / done'), suggesting it's for completed or abandoned cases. However, it does not explicitly state when to use this versus alternatives like 'resolve_case' or 'update_case', nor does it mention prerequisites or exclusions.

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