Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

Concat

Combines multiple string values into a single string, preserving a shared language tag or returning a plain xsd:string when tags differ.

Instructions

Concatenates multiple string values into a single string, per SPARQL's CONCAT() function: if all inputs carry the same language tag the result carries it too, otherwise the result is a simple (xsd:string) literal.

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": {
      "inputs": "<inputs>"
    },
    "name": "Concat"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYesArray of string values to concatenate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.8/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 it does disclose a genuine behavioral rule: language-tag propagation when all inputs share a tag, otherwise an xsd:string result. It says nothing about empty-array behavior, mixed literal types, or error handling, which is a meaningful gap for a fully unannotated tool.

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?

A single front-loaded sentence stating the operation first and the result-typing rule second, with no filler or restatement 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 one-parameter, no-annotation, no-output-schema tool, the description covers the operation and the result typing, which is the essential contract. Only edge-case behavior (empty inputs, mixed tags beyond the stated rule) is left 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% for the single `inputs` parameter, so the baseline is 3. The description does add a little meaning by implying inputs may be language-tagged literals rather than bare strings, but it gives no ordering, cardinality, or null-handling guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Concatenates multiple string values into a single string') and anchors it to a well-known external spec ('per SPARQL's CONCAT() function'), which lets an agent distinguish it from generic string-mutation siblings like Replace or Substitute without opening a schema.

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 through the reference to SPARQL's CONCAT() semantics; there is no explicit statement of when to pick this over Replace/Substitute or of preconditions. Adequate for a single-purpose expression helper, but nothing steers an agent between alternatives.

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