Skip to main content
Glama

delete_grid_placeholder

DestructiveIdempotent

Remove a placeholder tile from the grid. It is only a note and a slot — nothing is scheduled or published — but there is no undo.

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": {
      "workspace_id": "<workspace_id>",
      "placeholder_id": "<placeholder_id>"
    },
    "name": "delete_grid_placeholder"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
placeholder_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety bar is lower, and the description still adds real value: it quantifies the blast radius (nothing scheduled or published is lost) and states 'there is no undo,' which is more concrete than the destructive hint alone.

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?

Two short sentences, front-loaded with the action, the second sentence delivering the two facts that matter (no real-world side effects, irreversible). Nothing is padded or restated from the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need no explanation, and annotations cover the mutation profile. What remains missing is any guidance on the identifiers required to target the right placeholder and any note on permissions or failure cases for a destructive, non-undoable operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters, so the description carries the full burden — yet it never mentions workspace_id or placeholder_id, their formats, or how a placeholder is identified. 'From the grid' and 'placeholder tile' only faintly gesture at the two inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Remove a placeholder tile from the grid.' That is enough to separate it from create/convert/update_grid_placeholder siblings by name and effect, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: a placeholder is defined as 'only a note and a slot — nothing is scheduled or published,' which tells the agent this is safe in terms of side effects on real content. There is no explicit 'use this instead of convert_grid_placeholder when...' routing or prerequisite statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources