Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-AddSelect

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

Instructions

Creates a SPARQL SELECT query resource in a document.

    This tool creates a SPARQL SELECT 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:Select resource with the SPARQL query text
    - Posts the new SELECT 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-AddSelect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URI of the document to write the SELECT query to.
queryYesThe SPARQL SELECT query string.
titleYesTitle of the SELECT 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 SELECT query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

B3.4/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 key behavioral fact that the tool POSTs a new resource to the target document and clarifies the non-obvious service URI semantics (sd:Service, not endpoint URL). It omits permissions/auth requirements, whether an existing resource is overwritten, and what the response contains.

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?

Front-loaded with the core action, then a short bullet list of effects. There is mild redundancy: the service URI caveat appears in the prose and again verbatim in the schema, and the second paragraph largely restates the first.

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 six-parameter mutation with no annotations and no output schema, the description covers what is created and where it is posted. It does not describe the return value (e.g., the URI of the created resource), error or conflict behavior, or whether repeated calls create duplicates, which leaves meaningful gaps.

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 schema already documents all six parameters, including the service URI caveat. The description restates the optional fields and the service note without adding syntax, format, or constraint details beyond the schema. Baseline 3 applies.

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 and resource: 'Creates a SPARQL SELECT query resource in a document', and names the RDF type produced (sp:Select). It is distinguishable from ldh-AddConstruct by the SELECT-specific wording, but it never explicitly contrasts itself with that sibling.

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?

It gives downstream context ('can be used for charts, views, or other data processing operations'), which implies when the tool is useful. However, it offers no explicit when-to-use versus when-not guidance and does not point to ldh-AddConstruct, ldh-AddView, or ldh-AddResultSetChart as alternatives.

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