Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

GET

Fetches RDF data from a named graph URL and returns the RDF graph describing the resource for linked-data queries and processing.

Instructions

Retrieves RDF data from a named graph using HTTP GET. The URL serves as both the resource identifier and the named graph address in systems with direct graph identification. Returns the RDF graph describing the resource at that URL.

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>"
    },
    "name": "GET"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to fetch RDF data from. This should be a valid URL pointing to RDF content.

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 burden and does disclose the retrieval mechanism (plain HTTP GET) and the dual role of the URL, implying a read-only operation. It says nothing about authentication, redirects, 404/406 handling, or content negotiation for non-RDF responses.

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?

Three short sentences, front-loaded with the verb and mechanism; nothing is buried. The final sentence restates the return value already implied by the opening sentence, so a little redundancy remains.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema and no annotations, the description covers mechanism, scope assumption, and return value, which is close to sufficient. The main omissions are serialization formats and error behavior, which an agent would otherwise have to discover.

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 there is only one parameter, so the baseline is 3. The description adds a small amount of meaning by explaining that the URL doubles as resource identifier and named graph address, but gives no format or syntax 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?

States a specific verb and resource: 'Retrieves RDF data from a named graph using HTTP GET,' and clarifies that the URL acts as both identifier and graph address. It is clearly distinguishable from the write siblings (POST/PUT/PATCH), though it never names how it differs from query siblings like CONSTRUCT or DESCRIBE.

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 by the HTTP-GET framing and the conditional 'in systems with direct graph identification,' which hints at when the URL-identifies-the-graph assumption holds. There is no explicit guidance on when to choose this over CONSTRUCT or DESCRIBE, and no stated prerequisites.

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