Skip to main content
Glama

Remove a block

remove_block
Read-only

Delete one block from the document.

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": {
      "document": "<document>",
      "blockId": "<blockId>"
    },
    "name": "remove_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockIdYesThe id of a block in the document.
documentYesThe Publisle document: an object with schemaVersion and blocks, as returned by the other tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior1/5

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

The description describes a destructive mutation ("Delete one block") while the annotations declare readOnlyHint=true and destructiveHint=false, and it offers nothing to reconcile that. No statement clarifies whether the document is mutated in place, whether a new document is returned, or whether the deletion is reversible; the sentence actively misleads relative to the structured safety metadata.

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?

A single front-loaded sentence with zero waste, which is structurally sound. The brevity crosses into under-specification for a mutation tool with a nested document parameter and contradictory annotations.

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?

For a two-parameter tool with full schema coverage and no output schema, the minimum is largely met by the schema. However, a mutation whose annotations say read-only and non-destructive demands at least one sentence of reconciliation, and the nested document object's round-trip semantics are unaddressed.

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 both parameters (blockId and the nested document object) are already documented in the schema. The description adds no further meaning about accepted id formats, what happens with an unknown blockId, or how the passed document relates to the returned one, so the baseline of 3 applies.

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?

"Delete one block from the document" gives a specific verb (delete) and resource (block) with a scope qualifier. It is clear on its own, but it does nothing to distinguish itself from adjacent siblings such as update_block, move_block, or duplicate_block, which an agent must choose between.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent gets no signal about whether to reach for remove_block versus update_block when it wants to clear a block's content, or how to obtain the required document object beforehand.

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