Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

CONSTRUCT

Execute a SPARQL graph-building query against a remote endpoint or local RDF graph to produce derived triples.

Instructions

Executes a SPARQL CONSTRUCT query over an endpoint or over a graph in hand.

Input Schema

NameRequiredDescriptionDefault
graphNoA graph to query locally (or give 'endpoint')
queryYes
endpointNoSPARQL endpoint URL (or give 'graph')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It reveals the two execution modes but says nothing about what is returned (an RDF graph/triples), whether the operation is read-only, or what happens with an unreachable endpoint or malformed query.

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?

A single, front-loaded sentence with no filler. The dual-target condition is stated compactly without redundancy.

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?

There is no output schema and no annotations, so the description should explain the return value (a constructed RDF graph) and any endpoint-access caveats. As written, an agent knows how to call it but not what it will get back or how failures manifest.

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 67%, with graph and endpoint documented in the schema; the description's main added value is constraining 'query' to be a CONSTRUCT query specifically, which the schema's bare string type does not convey. It adds little beyond that.

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?

States a specific verb (executes) and resource (a SPARQL CONSTRUCT query), and names the two execution targets. The use of 'CONSTRUCT' implicitly distinguishes it from the SELECT/DESCRIBE siblings, though it never explicitly contrasts them.

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?

Implies the use case (you have a CONSTRUCT query to run) and notes that you supply either an endpoint or an in-hand graph. There is no explicit when-not guidance, no mention of when to prefer SELECT or DESCRIBE, and no prerequisites for remote endpoint access.

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