Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ExtractOntology

Extracts a complete OWL ontology (classes, datatype and object properties with functional restrictions) from an RDF dataset, optionally scoped to selected subjects via SPARQL bindings.

Instructions

Extracts a complete OWL ontology (classes, datatype properties, and object properties with functional property restrictions) from 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": "ExtractOntology"
  }
}

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.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does describe the return shape (an OWL ontology with the listed axiom types) and that it reads from a SPARQL endpoint, but it says nothing about read-only behavior, how many queries it issues, performance or size limits, failure modes for unreachable endpoints, or what happens when a subject has no extractable axioms.

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 with no filler; the parenthetical list of extracted axiom types is dense but earns its place by defining output scope. Slight loss for cramming the bindings scoping clause into the same sentence rather than separating it.

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 two-parameter tool with no annotations and no output schema, the definition covers the essential contract: source endpoint, optional subject scoping, and the content of the returned ontology. It remains thin on operational behavior (query strategy, size of result, errors) that an agent would want before invoking it against a live endpoint.

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 both parameters are already documented in the schema, including bindings as "Optional SELECT result whose ?subject column scopes the extraction." The description only restates that scoping optionally and never mentions 'endpoint' at all, adding no meaning 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?

Uses a specific verb and resource ("Extracts a complete OWL ontology") and enumerates exactly what is returned: classes, datatype properties, and object properties with functional property restrictions. That enumeration implicitly distinguishes it as the all-in-one superset of the sibling extractors (ExtractClasses, ExtractDatatypeProperties, ExtractObjectProperties), though it never names them.

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?

There is no explicit when-to-use or when-not statement, and no named alternative among the granular Extract* siblings. The only usage signal is implied: calling this returns all three component types at once, whereas the siblings return one each, so the choice is inferable but left to the agent.

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