clear_canvas
Remove all graphics from the current canvas to start fresh with a blank workspace.
Instructions
Remove all graphics from the current canvas
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Remove all graphics from the current canvas to start fresh with a blank workspace.
Remove all graphics from the current canvas
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states the effect but lacks details about irreversibility, confirmation prompts, or whether the action is undoable. However, it is straightforward and not misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that efficiently conveys the tool's purpose with no extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given there are no parameters and no output schema, the description is complete enough for a simple clearing tool. It could mention any return value or confirmation, but this is minor.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so schema description coverage is 100%. The description does not need to add parameter information, and baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Remove all graphics') and the target ('from the current canvas'), distinguishing it from sibling tools like delete_graphics which remove specific graphics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when clearing the entire canvas, but it does not explicitly state when to use this tool versus siblings like delete_graphics, nor does it provide context for when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Youn-17/omnigraffle-bindcraft'
If you have feedback or need assistance with the MCP directory API, please join our Discord server