Skip to main content
Glama
Sign In

tithonus

by org.tithonus
OverviewDiscussionsAdmin

tithonus_now

Read-only

Get a signed statement of the current UTC time from tithonus.org. It includes the latest drand round, so anyone can see it was made after that moment. Use when you need trustworthy current time, or proof of when you asked. Pass a fresh nonce to bind the answer to your request.

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

Input Schema

NameRequiredDescriptionDefault
nonceNoOptional. Any string; long or unusual ones are signed as their sha256.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral context beyond the annotations: the result is a signed statement, includes the latest drand round, and can be bound to a request via a fresh nonce.

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?

The description is front-loaded with the core purpose and then adds only useful details about drand, usage, and nonce binding. It is appropriately sized and every sentence contributes to correct selection or invocation.

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 simple read-only tool with one optional parameter, no output schema, and annotations covering safety, the description is complete enough. It explains the return content, the usage context, and the nonce's role without requiring additional fields.

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 schema already documents the single nonce parameter at 100% coverage. The description adds meaning beyond the schema by explaining that a fresh nonce binds the answer to the caller's request, which clarifies why an optional parameter is useful.

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 verb and resource: 'Get a signed statement of the current UTC time from tithonus.org.' It also explains the drand inclusion, but it does not distinguish this tool from siblings such as tithonus_beacon or tithonus_stamp.

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

Usage Guidelines4/5

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

It gives clear usage context: 'Use when you need trustworthy current time, or proof of when you asked.' It does not name when-not conditions or explicit alternatives, so it falls just short of full routing guidance.

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

All tithonus toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources