headlo-mcp

Official

by headlohq

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

delete_module

Remove a module from a page by providing its module ID and confirming deletion.

Instructions

Remove a module from 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": {
      "module_id": "<module_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_module"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Must be true to confirm deletion
`module_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Behavioral transparency is low. The description only states the action 'Remove', but does not disclose that deletion is permanent, requires confirmation (despite the confirm parameter), or any cascading effects. With no annotations available, the description fails to carry the burden of explaining the destructive nature and safety requirements.

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?

The description is an efficient single sentence that immediately communicates the action and object. It is appropriately sized and front-loaded with no redundant wording.

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 destructive operation with a confirmation parameter, the description is incomplete. It lacks critical context about irreversibility, the confirmation requirement, and any side effects. The absence of output schema and annotations makes the description's brevity a significant gap.

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?

The description adds no parameter-level information. While the schema documents the 'confirm' parameter with a description, 'module_id' has no description and the description text does not explain either parameter beyond what the schema provides. With 50% schema coverage, the description should have compensated but does not.

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

Purpose5/5

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

The description uses a specific verb 'Remove' with a clear resource 'module' and location 'from a page', clearly distinguishing it from sibling tools like create_module, update_module, and get_module. It succinctly conveys the tool's core function.

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?

No usage guidance is provided. The description does not mention when this tool should be used over alternatives, nor does it state any prerequisites or scenarios. For example, there is no mention that users should confirm before deletion or that this is for removing a module from a page versus editing it.

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