Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ExtractDatatypeProperties

Extract OWL datatype properties from literal-valued RDF predicates, optionally scoped to subjects in provided bindings. Use it to identify datatype properties from a SPARQL endpoint dataset.

Instructions

Extracts OWL datatype properties from literal-valued predicates in an RDF dataset, optionally scoped to the subjects in 'bindings'.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "ExtractDatatypeProperties"
  }
}

Input Schema

NameRequiredDescriptionDefault
bindingsNoOptional SELECT result whose ?subject column scopes the extraction to those subjects
endpointYesSPARQL endpoint URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.5/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 disclosure burden. It implies a read-only extraction over an RDF dataset and explains the scoping behavior of 'bindings', but says nothing about the network access to the endpoint, whether results are deduplicated, or what happens with missing/literal-less predicates.

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

Conciseness5/5

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

A single sentence that front-loads the core action and appends the optional scoping caveat. No filler or redundancy.

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 tool is simple (2 params, one required) and has no output schema, so the description need not explain return values in depth — but it is silent on the output form (graph, triples, or property list) and on endpoint requirements, leaving an agent guessing about results.

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 both parameters, setting the baseline at 3. The description restates the 'bindings' scoping idea (subjects scope the extraction), which adds modest reinforcement but no syntax or format detail beyond the schema.

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 ('Extracts') and resource ('OWL datatype properties from literal-valued predicates in an RDF dataset'), which is enough to separate it from object-property or class extraction siblings by the datatype/literal qualifier. It stops short of naming a sibling explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied: the tool applies to literal-valued predicates and can be narrowed with 'bindings'. There is no explicit when-to-use versus when-to-use-another-tool statement, and no prerequisites (e.g., that a reachable SPARQL endpoint is required) are spelled out.

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