Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

PUT

Replaces RDF data in a named graph by sending a JSON-LD payload to a URL, confirming success without returning the updated graph.

Instructions

Replaces RDF data in a named graph using HTTP PUT. The URL serves as both the resource identifier and the named graph address in systems with direct graph identification. Completely replaces the RDF graph (provided as JSON-LD payload) at that URL. 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>",
      "data": "<data>"
    },
    "name": "PUT"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to send the RDF data to. This should be a valid URL.
dataYesThe RDF data to send, represented as a JSON-LD dict.

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 provided, so the description must carry the behavioral burden, and it does most of that work: it discloses that the whole graph is destroyed and replaced, that it returns a boolean, and explicitly that the updated graph is not returned. The gaps are permissions and authentication needs, plus what happens to existing data if the PUT fails midway.

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 definition is front-loaded with the core action and organized as short statements, with no filler in the opening. The closing note overlaps with the earlier "Returns True ... False otherwise" sentence, so it is slightly redundant, even if that redundancy helps emphasize that no graph is returned.

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?

With no annotations and no output schema, the description must cover side effects and returns; it covers the overwrite semantics and the boolean return, which is good. However, it is silent on failure semantics (whether a failed PUT leaves the graph empty), on permissions, and on whether a missing graph is created, and these matter for a destructive full-replace operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a score of 3 is the baseline, but the description adds real meaning: the URL serves as both the resource identifier and the named-graph address in systems with direct graph identification, which goes beyond the schema's generic "The URL to send the RDF data to." The data parameter is only restated as a JSON-LD payload.

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: it replaces RDF data in a named graph via HTTP PUT, and it states that the replacement is complete. That makes a meaningful distinction from operations that partially change data, but no sibling (POST, PATCH, Replace) is named, so the comparison is only implicit.

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 phrase "Completely replaces the RDF graph" implies when this tool is appropriate instead of a partial-update tool, but the definition never names an alternative or gives any exclusion condition. What guidance exists is inferred rather than stated.

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