Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-RemoveBlock

Removes a content block from a LinkedDataHub document via SPARQL UPDATE, optionally targeting a specific block URI, to clean up document sequence references and block properties.

Instructions

Removes a content block from a LinkedDataHub document.

    This tool removes content blocks from LinkedDataHub documents by:
    - Deleting the sequence property that references the block (rdf:_N)
    - Deleting all properties of the block itself
    - If no specific block URI is provided, removes any blocks found via sequence properties
    
    The operation uses SPARQL UPDATE (HTTP PATCH) to perform the deletion.

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": {
      "url": "<url>"
    },
    "name": "ldh-RemoveBlock"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URI of the document to remove the block from.
blockNoOptional URI of the specific content block to remove. If not provided, will remove blocks based on sequence properties.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses the exact destructive effects (deleting the rdf:_N sequence property and all properties of the block) and the transport used (SPARQL UPDATE over HTTP PATCH). It omits reversibility, permission requirements, and the response shape, which keeps it from a 5.

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?

The leading sentence is front-loaded and the bulleted breakdown of deletion steps is easy to scan. Slight redundancy remains, since the opening clause is re-stated verbatim in the second sentence, but nothing is padded beyond that.

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

Completeness4/5

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

For a two-parameter destructive tool with no annotations and no output schema, the description covers the operation target, the destructive scope, and the transport. What is missing are the post-condition details an agent might want (effect on other triples, error behavior, whether deletion is reversible).

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 the baseline is 3, and the description largely restates the schema's account of block ('if no specific block URI is provided...'). It adds mild value by naming the rdf:_N sequence mechanism that resolves the optional parameter, but no format or URI-syntax detail beyond the schema.

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 ('Removes a content block from a LinkedDataHub document') and spells out the deletion mechanics, so an agent can distinguish it from the ldh-Add* siblings. It stops short of explicitly naming the counterpart add tool, so the differentiation is implied by the verb rather than stated.

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 declared: the description explains that omitting block 'removes any blocks found via sequence properties', which is a useful conditional but not a when-to-use/when-not-to-use rule. There is no guidance on alternatives (e.g. adding or replacing blocks) or on prerequisites, so the agent must infer the scenario.

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