Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-AddConstruct

Creates and posts a SPARQL CONSTRUCT query resource to a LinkedDataHub document so you can execute or reference it in charts, views, and data processing.

Instructions

Creates a SPARQL CONSTRUCT query resource in a document.

    This tool creates a SPARQL CONSTRUCT query that can be executed and referenced within LinkedDataHub.
    The query can be used for charts, views, or other data processing operations.
    
    This tool:
    - Creates a sp:Construct resource with the SPARQL query text
    - Posts the new CONSTRUCT query resource to the target document
    - Supports optional title, description, fragment identifier, and service URI
    Note: the service URI is _not_ the SPARQL endpoint URL but an instance of `sd:Service` that describes the SPARQL service capabilities (and contains the endpoint URL).
    The service URI can be used to reference the SPARQL service in other operations.
    

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>",
      "query": "<query>",
      "title": "<title>"
    },
    "name": "ldh-AddConstruct"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URI of the document to write the CONSTRUCT query to.
queryYesThe SPARQL CONSTRUCT query string.
titleYesTitle of the CONSTRUCT query.
serviceNoOptional URI of the SPARQL service/endpoint specific to this query. Note: the service URI is _not_ the SPARQL endpoint URL but an instance of `sd:Service` that describes the SPARQL service capabilities (and contains the endpoint URL).
fragmentNoOptional fragment identifier for the query URI (e.g., 'my-query' creates #my-query).
descriptionNoOptional description of the CONSTRUCT query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the concrete write action (posts a sp:Construct resource to the target document) and clarifies the non-obvious meaning of the service URI (an sd:Service, not an endpoint URL). It says nothing about required permissions, behavior on name collision, or what is returned after creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bulleted effect list is useful and the purpose is front-loaded. However, the second paragraph largely restates the first sentence's purpose, and the service-URI note is duplicated verbatim between description and schema, which is avoidable repetition.

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 mutation tool with no annotations and no output schema, the definition covers what is created and where, but leaves out permissions, error/failure conditions, and the result of the call (e.g., the URI of the new resource). Those gaps matter for an agent deciding how to invoke and verify the operation.

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 description coverage is 100%, so all six parameters are already documented, which sets the baseline at 3. The description's list of optional fields and its service-URI caveat just restate schema content rather than adding new semantics, so it neither exceeds nor falls below the baseline.

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 first sentence names a specific verb and resource: 'Creates a SPARQL CONSTRUCT query resource in a document.' It also enumerates the concrete effects (creates sp:Construct, posts to the target document). It does not, however, distinguish itself from the sibling ldh-AddSelect, which likely creates SELECT query resources, leaving the query-type choice to inference.

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 description gives downstream context ('can be used for charts, views, or other data processing operations'), which implies when it is useful. It never states when NOT to use this tool or names an alternative such as ldh-AddSelect for SELECT queries, so the usage boundary remains implicit.

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