Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ExtractClasses

Extracts OWL class candidates from rdf:type statements in an RDF dataset, optionally limiting results to subjects in a provided bindings result.

Instructions

Extracts OWL classes (owl:Class candidates) from rdf:type usage 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": "ExtractClasses"
  }
}

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 behavioral burden. It does disclose the key mechanism, deriving owl:Class candidates from rdf:type usage and optionally scoping by subjects, but it does not explicitly state that the operation is read-only, whether it performs a remote SPARQL query, or what kind of result is returned.

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?

The description is a single, front-loaded sentence with no wasted wording. It communicates the core extraction behavior and the optional scoping parameter efficiently.

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 simple two-parameter extraction tool with full schema coverage, the description covers the main operation and optional scoping. However, since there is no output schema, it could do more to describe the expected return shape or what happens when no classes are found.

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. The description reinforces that 'bindings' is an optional subject-based scope and that 'endpoint' identifies the RDF dataset, but it does not add significant syntax or format details 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 states a specific verb and resource: extracting OWL classes from rdf:type usage. It also clarifies the optional scoping mechanism. It does not explicitly distinguish itself from siblings such as ExtractDatatypeProperties or ExtractObjectProperties, but the resource type makes the distinction fairly clear.

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 indicates that extraction can optionally be scoped to subjects in 'bindings', which implies when the optional parameter should be used. However, it provides no explicit guidance on when to choose this tool over sibling extraction tools, and no exclusions or prerequisites are stated.

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