Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

Now

Returns the run-start date and time as a fixed UTC xsd:dateTime literal, matching SPARQL NOW() so every call within one program run yields the same value.

Instructions

Returns the current date and time as an xsd:dateTime literal in UTC, following SPARQL's NOW(): every Now in one run of a program returns the same value, the time the run began.

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": "Now"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses UTC, the literal datatype, and the non-obvious evaluation semantics that every call within one run returns the run-start time. It does not explicitly say the operation is pure/side-effect-free, which is the only remaining behavioral gap for a zero-argument function.

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 sentence, front-loaded with the return value, followed by format and then the subtle determinism caveat. Every clause adds information an agent would otherwise have to guess.

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

Completeness5/5

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

For a zero-parameter, side-effect-free function with no output schema, the description supplies everything needed: what is returned, its datatype and timezone, and how repeated calls behave within a run.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-related noise is introduced.

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 ('Returns the current date and time') plus the exact return representation (xsd:dateTime literal in UTC). It does not explicitly contrast with a sibling such as StrUUID, which is the one nearby generator-style tool, so it stops short of a 5.

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 implied rather than stated: an agent can infer this is the way to obtain a timestamp, and the determinism note signals when to rely on it. There is no explicit when-to-use/when-not or named alternative, so it lands at the minimum-viable tier.

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