Skip to main content
Glama

block_disconnect

Removes a connection between two blocks on a page, disconnecting the link between specified blocks and their optional connectors.

Instructions

Removes a connection between two blocks on a page.

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": {
      "from_block": "<from_block>",
      "to_block": "<to_block>"
    },
    "name": "block_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
to_blockYes
from_blockYes
to_connectorNo
from_connectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.8/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 behavioral burden and does not meet it. It says nothing about whether the disconnect is reversible, whether it errors when no such connection exists, whether it affects only one direction, or what permissions are required for the page.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but brevity here comes at the cost of under-specification rather than efficiency. There is no structure to speak of beyond the one clause.

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

Completeness2/5

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

For a mutation tool with five parameters, zero schema descriptions, no annotations, and no output schema, one sentence is not enough. The agent must guess at connector semantics and at mutation safety, which are exactly the gaps structured fields would otherwise fill.

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 coverage is 0% across five parameters, and the description only implies from_block/to_block via 'between two blocks.' The optional page, from_connector, and to_connector parameters are left entirely unexplained, with no hint that connectors can disambiguate which link is severed when multiple connections exist.

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 gives a specific verb and resource: 'Removes a connection between two blocks on a page.' An agent can distinguish this from block_connect by the verb alone. It stops short of naming the inverse operation explicitly, but the purpose is unambiguous.

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 is only implied: you call it when an existing connection should be gone. There is no statement about preconditions (does the connection need to exist?), no mention of the counterpart block_connect, and no guidance on when a different tool (e.g. block_remove) is the right choice instead.

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