Skip to main content
Glama
fusion-cam

fusion-cam

close_scratch

Discard unsaved documents created by import_step without saving them, closing one by scratch_id or name or all of them. It never closes the user's own documents.

Instructions

Close, WITHOUT saving, documents that import_step created and that were never saved.

name=None closes all of them; with a name, only that document, and it refuses (with the reason) if the document was not created by import_step or has been saved. scratch_id (returned by import_step) selects exactly one document; prefer it, because imported documents are often named "Untitled" like the user's own. Never closes the user's documents. A timed-out call may still finish: call status before retrying.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "close_scratch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
timeout_sNo
scratch_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it discloses that nothing is saved, that the call can refuse with a reason, the precise refusal conditions, that user documents are never touched, and the non-obvious hazard that a timed-out call may still complete. This is behavior beyond what any schema field conveys.

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 non-destructive-to-user-data guarantee, and nearly every clause carries information an agent needs. The middle sentence runs long with stacked clauses, which slightly hurts scannability but not correctness.

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 3-parameter mutation tool with no annotations but an output schema, the description covers the risky parts: what is and is not destroyed, refusal conditions, parameter precedence, and retry safety after a timeout. Return-value detail is rightly left to the output schema.

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?

Schema coverage is 0%, so the description must compensate, and it does for two of three parameters: name (None vs. a name, plus refusal semantics) and scratch_id (its provenance from import_step and its precedence over name). timeout_s is never described beyond its name and the generic timeout note, leaving that one parameter thin.

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 (close) and a precisely bounded resource: documents created by import_step that were never saved. The negative scope ('WITHOUT saving', 'Never closes the user's documents') makes it immediately distinguishable from any generic close/document tool.

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 selection logic: name=None closes all, a name closes one but refuses if the document was not created by import_step or was already saved. It also prefers scratch_id over name with a concrete reason (imported docs are often named 'Untitled') and names the follow-up action after a timeout (call status before retrying).

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