Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

ResolveURI

Resolves a pre-encoded relative URI against a base URL to create a new absolute URI. Use it to construct accurate resource links for RDF and Linked Data workflows.

Instructions

    Creates a new URI relative to the base URL. The relative URI **must** be pre-encoded.
    

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": {
      "base": "<base>",
      "relative": "<relative>"
    },
    "name": "ResolveURI"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesThe base URI to resolve against.
relativeYesThe relative URI to resolve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.7/5.0
Behavior3/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 adds one genuinely useful behavioral constraint (input must already be encoded, so no encoding is performed here), but says nothing about error behavior for malformed or absolute inputs, or about the shape of the returned URI.

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?

Two short sentences, front-loaded with the operation and followed immediately by the one constraint that matters. There is no redundant wording or restating of the tool name.

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 two-parameter pure function with fully documented parameters and no output schema, this is nearly sufficient. A brief note on what is returned (absolute URI string) or on failure conditions would close the remaining gap, but nothing critical to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns an extra point by imposing a meaningful constraint on the 'relative' parameter (pre-encoded) that the schema's generic 'The relative URI to resolve.' does not convey. The 'base' parameter gains no additional semantics.

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 operation on a specific resource: resolving a relative URI against a base to produce a new URI. It is clearly distinguishable from siblings like EncodeForURI or Concat, though the sibling routing is only implicit via the pre-encoding note rather than stated outright.

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 note that the relative URI 'must be pre-encoded' implies the agent should call EncodeForURI first, but no alternative is named and no explicit when-to-use/when-not-to-use guidance is given. Usage is inferable rather than stated.

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