Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ExtractObjectProperties

Extracts OWL object and functional properties (closed-world) from IRI-valued RDF predicates, optionally scoped to subjects in a bindings SELECT result.

Instructions

Extracts OWL object properties (and functional properties, closed-world) from IRI-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": "ExtractObjectProperties"
  }
}

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

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 disclosure burden, and it does contribute real behavioral context: the closed-world assumption, the inclusion of functional properties, and the subject-scoping effect of 'bindings'. However, it says nothing about what is returned, whether the endpoint is queried exhaustively (load/cost implications), or how errors are surfaced, leaving meaningful gaps for a no-annotation tool.

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 that opens with the verb and resource, with the optional scoping clause at the end where it belongs. Dense and jargon-heavy but every clause carries information; nothing is redundant.

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?

There are no annotations and no output schema, so the description must cover both behavior and results, and it only covers the former. An agent still does not know the shape of the output (axiom set, triple list, ontology document) or how it is delivered, which is a notable gap for a tool whose whole purpose is producing a derived structure.

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% and the schema already explains that 'bindings' is an optional SELECT result whose ?subject column scopes extraction, and that 'endpoint' is a SPARQL endpoint URL. The description restates the same optional-scoping idea without adding format, syntax, or edge-case detail, so the baseline 3 is appropriate.

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?

Names a specific verb and resource ('Extracts OWL object properties ... from IRI-valued predicates in an RDF dataset') and even qualifies the scope with the closed-world/functional caveat. The qualifier 'IRI-valued predicates' implicitly distinguishes it from the datatype-property sibling without naming it, so an agent can tell the two apart from the description alone.

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 only implied: the tool clearly applies when you have a SPARQL endpoint and want object (IRI-valued) properties, and the 'bindings' clause hints at a follow-on workflow after a SELECT. There is no explicit when-to-use/when-not statement, no mention of ExtractDatatypeProperties as the alternative for literal-valued properties, and no stated prerequisites for the endpoint.

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