Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

POST

Creates or appends a named RDF graph at a given URL by sending JSON-LD data; returns success only, not the updated graph.

Instructions

Creates or appends RDF data to a named graph using HTTP POST. The URL serves as both the resource identifier and the named graph address in systems with direct graph identification. Creates or adds to 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": "POST"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose the return contract (True on success, False otherwise) and explicitly notes that the updated graph is not returned, which is exactly the kind of context an agent needs. It stops short of covering error/partial-write behavior, idempotency, or authentication requirements for a mutating HTTP operation.

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 operation and its contract are front-loaded, and the note about not returning the updated graph is well placed. There is mild redundancy between 'Creates or appends RDF data' and 'Creates or adds to the RDF graph', which restates the same idea in slightly different words.

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?

For a two-parameter write tool with no annotations and no output schema, the definition covers the essentials: the write semantics, the graph-addressing role of the URL, and the boolean return contract. It remains thin on failure modes and preconditions, which matter for a mutating HTTP call that an agent may retry or chain.

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 the baseline would be 3, but the description earns extra credit by explaining that the url parameter functions as both the resource identifier and the named graph address in systems with direct graph identification. That is genuine meaning beyond the schema's terse 'The URL to send the RDF data to'. The data parameter's JSON-LD payload semantics are already fully covered by 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 gives a specific verb+resource pair: creates or appends RDF data to a named graph via HTTP POST, and clarifies that the URL doubles as both resource identifier and graph address. It is clear what the tool does, but it never contrasts itself with the sibling PUT or PATCH, which is the ambiguity an agent most needs resolved given a name as generic as 'POST'.

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 'Creates or appends' and 'Creates or adds to the RDF graph' imply that this is the additive, non-replacing write path, which hints at when to choose it. However, there is no explicit when-to-use or when-not-to-use guidance and no mention of PUT/PATCH/Replace as the alternatives, so the routing decision is left to inference.

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