Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ldh-AddGenericService

Create and post a generic SPARQL service description to a LinkedDataHub document, defining an sd:Service endpoint with supported languages for reference and use.

Instructions

Writes a generic SPARQL service description to a LinkedDataHub document.

    This tool creates a SPARQL service description that can be referenced and used within LinkedDataHub.
    The service description includes endpoint information and supported capabilities.
    
    This tool:
    - Creates an sd:Service resource with endpoint URI and supported languages
    - Posts the new service description to the target document
    - Supports optional title, description, fragment identifier, graph store, and authentication
    - Automatically sets SPARQL 1.1 Query and Update support

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>",
      "endpoint": "<endpoint>",
      "title": "<title>"
    },
    "name": "ldh-AddGenericService"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URI of the document to write the service to.
titleYesTitle of the service.
auth_pwdNoOptional authorization password for the service.
endpointYesEndpoint URI of the SPARQL service.
fragmentNoOptional fragment identifier for the service URI (e.g., 'my-service' creates #my-service).
auth_userNoOptional authorization username for the service.
descriptionNoOptional description of the service.
graph_storeNoOptional Graph Store URI for the service.

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses that the tool creates an sd:Service resource, posts to the target document, and automatically sets SPARQL 1.1 Query and Update support. It does not explain permission requirements, whether an existing service is overwritten, failure behavior, or 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?

The description is front-loaded with the main action and uses a short bullet list to enumerate behavior. There is mild redundancy between the opening sentence and the following 'This tool creates...' sentence, but overall it is efficient and easy to scan.

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?

The description is adequate for an 8-parameter mutation tool with no output schema, covering the created resource and key optional fields. It leaves gaps around authentication requirements, target document constraints, and overwrite behavior, which an agent might need before invoking the tool.

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 every parameter is already documented in the schema. The description lists the optional fields (title, description, fragment, graph store, authentication) but adds little semantic detail beyond what the schema provides, so the baseline score of 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?

The description states a specific verb and resource: 'Writes a generic SPARQL service description to a LinkedDataHub document,' and clarifies it creates an sd:Service resource. It does not explicitly contrast itself with siblings like ldh-AddSelect or ldh-AddConstruct, but the phrase 'generic SPARQL service description' distinguishes it reasonably well.

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 implied usage context by saying the service description 'can be referenced and used within LinkedDataHub,' indicating this is for registering an endpoint. However, it does not state when to use this tool versus ldh-AddSelect, ldh-AddConstruct, or other sibling tools, nor does it mention prerequisites or exclusions.

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