Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

Merge

Combines multiple JSON-LD RDF graphs into a single unified RDF graph, enabling consolidated data processing and simpler downstream queries.

Instructions

Merges a list of RDF graphs as JSON-LD dicts into a single RDF graph as JSON-LD.

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": {
      "graphs": "<graphs>"
    },
    "name": "Merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphsYesList of JSON-LD objects to merge into a single RDF graph.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain merge semantics such as duplicate-triple handling, blank-node treatment, input mutation, ordering, or error behavior.

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?

The definition is a single front-loaded sentence with no filler. It is slightly repetitive in phrasing ('JSON-LD dicts' and 'as JSON-LD'), but this does not impair clarity.

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 one-parameter utility with full schema coverage and no output schema, the description is adequate but incomplete. It says what input and output types are, yet leaves important merge behavior unspecified.

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%, and the single parameter is already documented as a list of JSON-LD objects. The description restates that meaning but adds no extra syntax, constraints, or examples beyond the schema baseline.

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 names a specific verb ('Merges') and resource ('list of RDF graphs as JSON-LD dicts' into 'single RDF graph as JSON-LD'). It is clear what the tool does, but it does not distinguish this operation from potential siblings such as Concat or Replace.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states only what the tool does, with no when-to-use guidance, prerequisites, or comparison to alternatives. An agent must infer that this is the right tool whenever multiple JSON-LD graphs need to be combined.

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