Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-List

Lists child documents for a given URL and returns them as SPARQL results JSON, enabling discovery of linked resources under a document hierarchy.

Instructions

Returns a list of children documents for the given URL as SPARQL results JSON.

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>"
    },
    "name": "ldh-List"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the document to list children for.
baseNoBase URL for constructing the SPARQL endpoint. Needs to end with a slash. Either 'endpoint' or 'base' must be provided.
endpointNoThe SPARQL endpoint URL to query. Either 'endpoint' or 'base' must be provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add useful behavioral context by declaring the response is SPARQL results JSON, which compensates for the absent output schema. However, it says nothing about read-only behavior, permissions, failure modes, or size/pagination characteristics of the returned list.

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 no wasted wording. It is efficient, though its brevity leaves the definition under-specified rather than richly trimmed.

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 low-complexity, single-purpose list tool with fully described parameters, the core call information is present and the return format is stated. Missing are usage guidance and any behavioral caveats, which matter more given the complete absence of annotations and an output schema.

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 all three parameters are already documented in the input schema, including the either/or constraint between 'base' and 'endpoint'. The description adds no additional meaning beyond that, which is the expected baseline when the schema does the work.

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: 'Returns a list of children documents for the given URL'. It also names the output format (SPARQL results JSON). It does not, however, differentiate this tool from similarly named siblings such as ldh-AddConstruct or ldh-AddFile, so an agent gets a clear purpose but no explicit contrast.

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?

There is no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The only implied usage is that a URL is required, which the schema already states. The agent must infer the selection context entirely.

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