Skip to main content
Glama

block_update

Edit a block's SOURCE content (Slate JSON). Note: edits live on the block, not in the stored source file — a later document_resync_source re-parses the file and overwrites them.

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": {
      "block_id": "<block_id>",
      "original_content": "<original_content>"
    },
    "name": "block_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idYes
block_typeNo
original_contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose one genuinely valuable trait — edits live on the block and are overwritten by a later resync — but it says nothing about permissions, whether the change is reversible, how conflicts are handled, or what a success response looks like for a mutation tool.

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 sentences, zero waste, with the core action front-loaded and the persistence caveat immediately after. Every clause earns its place.

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?

No annotations and no output schema, so the description must justify itself fully; the overwrite warning is the most important thing an agent needs and it is present. But the unexplained required original_content parameter and the absence of any failure/concurrency context leave a meaningful gap for a mutation tool.

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% across 3 parameters, so the description must compensate and largely does not. It clarifies that content is Slate JSON, but never explains whether original_content is the new content or the prior content used for concurrency control — a critical ambiguity given the parameter's name and required status. block_id and block_type are left entirely to inference.

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?

States a specific verb and resource: editing a block's SOURCE content, with the data format named (Slate JSON). It also implicitly distinguishes itself from block_translation_update by emphasizing SOURCE, though it never names that sibling as an alternative.

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?

The resync note effectively warns about a usage condition (edits are lost when document_resync_source re-parses the file), which is real guidance. However, it never says when to pick this over block_translation_update or document_update, so the alternative-selection guidance is only implied.

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