Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

DESCRIBE

Run a SPARQL resource-description query against a remote endpoint or local RDF graph to retrieve and inspect linked-data descriptions.

Instructions

Executes a SPARQL DESCRIBE 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

C2.9/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 does not say whether the query is read-only, what happens on remote endpoint access (auth, rate limits, timeouts), or what form the result takes (RDF triples/descriptions vs. rows). Only the bare operation is disclosed.

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 front-loaded sentence with zero filler; the operation and both query targets appear immediately. It is taut with no wasted wording, though the terseness is what leaves the gaps noted in other dimensions.

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?

For a SPARQL execution tool with no output schema and no annotations, the definition should describe the return shape (RDF graph / descriptions) and remote-endpoint behavior. Neither is present, and the undescribed 'query' parameter carries the most complex semantics.

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% and the schema already encodes the endpoint/graph mutual exclusion via oneOf plus per-parameter hints. The description restates the two-source choice but adds nothing about query syntax expectations or how the chosen source affects behavior.

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 specific resource ('SPARQL DESCRIBE query'), and scopes it to two query targets. An agent can distinguish this from CONSTRUCT/SELECT by the DESCRIBE form, though the description 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'over an endpoint or over a graph in hand' implies the two modes but gives no when-to-use rule, no prerequisites, and no steering toward or away from sibling query forms like CONSTRUCT or SELECT. The agent must infer selection from the name alone.

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