Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

PATCH

Updates RDF data in a named graph by sending a single SPARQL INSERT/WHERE or DELETE WHERE operation to a URL, returning success or failure without returning the updated graph.

Instructions

    Updates RDF data in a named graph using HTTP PATCH with SPARQL Update.
    The URL serves as both the resource identifier and the named graph address in systems with direct graph identification.
    Updates the RDF graph at that URL using the SPARQL update payload provided in the `update` argument.
    Only INSERT/WHERE and DELETE WHERE forms of SPARQL Update are supported by PATCH! Only a single update operation is allowed.

    Returns True if the operation was successful, False otherwise.
    Note: This operation does not return the updated graph, it only confirms the success of the operation.
    

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>",
      "update": "<update>"
    },
    "name": "PATCH"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to send the SPARQL UPDATE to. This should be a valid URL.
updateYesThe SPARQL update string to execute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the supported SPARQL Update subset, the single-operation limit, the boolean return value, and explicitly warns that the updated graph is not returned. It stops short of stating authorization requirements, error/exception behavior, or that DELETE WHERE can remove data irrevocably.

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?

The purpose and the hard constraints are front-loaded, which is good. But the third sentence ('Updates the RDF graph at that URL using the SPARQL update payload provided in the `update` argument') largely restates sentence one, and the closing note overlaps with the already-stated boolean return value, so a third of the text is repetition.

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 mutation tool with no annotations and no output schema, the description covers mechanism, constraints, and return semantics adequately. The remaining gap is operational context: nothing about authentication against the target endpoint or how failures manifest beyond a False return.

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 coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds real meaning for `url` (it is simultaneously the resource identifier and the named graph address) and constrains `update` to specific SPARQL forms, but supplies no syntax examples or payload formatting guidance.

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 opening sentence names a specific verb (updates), a specific resource (RDF data in a named graph), and the exact mechanism (HTTP PATCH with SPARQL Update), which separates it from the GET/PUT/POST siblings in the same family. It never names those alternatives explicitly, so differentiation is inferable 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?

The description gives hard constraints on when this tool is applicable (only INSERT/WHERE and DELETE WHERE forms, only a single update operation), which is useful selection guidance. However it never says 'use PUT instead when you want to replace the whole graph' or 'use POST when adding a new graph', so the agent must infer PATCH-vs-PUT routing from HTTP convention alone.

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