Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

StrUUID

Generates a fresh UUID string on every call for unique identifiers in RDF, linked-data, and SPARQL workflows.

Instructions

Generates a fresh UUID (Universally Unique Identifier) as a string, following the behavior of SPARQL's STRUUID(). Each invocation produces a new unique identifier.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "StrUUID"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A3.8/5.0
Behavior4/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 key behavioral trait: each invocation yields a new unique value, so the agent knows the call is non-deterministic and non-idempotent. It does not state the UUID variant/version or format details, which is a minor remaining gap.

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 compact sentence with the essential meaning front-loaded. The trailing clause 'Each invocation produces a new unique identifier' is largely redundant with 'fresh' and 'Universally Unique', costing a little tightness but reinforcing a behaviorally important point.

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 zero-parameter generator with no output schema, the description supplies what an agent needs: the return type (string) and the freshness guarantee. Only the concrete UUID format/version is unspecified, which is a small gap for this level of complexity.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema, which is empty and fully described. The baseline of 4 applies for a no-parameter tool.

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 and resource ('Generates a fresh UUID ... as a string') and anchors it to a known semantics ('following the behavior of SPARQL's STRUUID()'), which lets an agent distinguish it from sibling generators like Now. It does not explicitly contrast with any sibling by name, but the resource itself is unambiguous.

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: an agent can infer this is the tool to call when a unique identifier is needed. There is no explicit when-to-use vs when-not-to-use statement, no mention of alternatives (e.g., Now for timestamps, SPARQLString for literals), and no stated constraints.

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