Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

SELECT

Executes SPARQL queries over a remote endpoint or local graph to retrieve matching RDF data.

Instructions

Executes a SPARQL SELECT query over an endpoint or over a graph in hand

Input Schema

NameRequiredDescriptionDefault
graphNoA graph to query locally (or give 'endpoint')
queryYesSPARQL SELECT query
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 whole behavioral burden and does not say that SELECT is a read-only operation, whether results are truncated or paginated, how large a result set may be, or what authentication an endpoint might require. The only disclosed trait is the endpoint-vs-local-graph duality, which is already encoded in the schema's oneOf.

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?

A single tight sentence with the resource front-loaded and no filler. It is arguably slightly too terse for the ambiguity around query forms, but nothing is wasted.

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 3-parameter tool with full schema coverage and no output schema, the definition is minimally sufficient to invoke. It omits the return shape (variable bindings), result-size behavior, and error behavior for unreachable endpoints — gaps an agent would want before issuing a query.

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 the baseline is 3; the description adds essentially nothing beyond the schema, which already states 'or give endpoint' / 'or give graph'. It does not explain expected URL format, whether the graph is a URI or an in-memory dataset, or any query-string constraints.

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 (executes) and resource (a SPARQL SELECT query) plus the two execution targets (endpoint or local graph), which is enough to identify the operation. It stops short of distinguishing itself from query-form siblings such as CONSTRUCT or DESCRIBE, so an agent still has to infer that SELECT returns bindings rather than triples.

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 is only implied by the structural choice 'over an endpoint or over a graph in hand', which mirrors the oneOf in the schema rather than stating when to pick each. There is no guidance on when to use SELECT versus CONSTRUCT/DESCRIBE, nor any mention of prerequisites such as a reachable endpoint.

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