Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

time

[x402 paid: $0.003 USDC on Base] Current time: UTC ISO string, unix timestamp and any IANA timezone. tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault
tzNoexample: Europe/Moscow

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose notable traits: this is an x402-paid call costing $0.003 USDC on Base, and a tools/call returns the live payment challenge. It does not say what happens with an invalid or unsupported tz, whether returned timezone list is derived from the argument, or whether payment is required on every invocation.

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?

Two compact sentences, front-loaded with the return formats. The bracketed price tag occupies prime real estate ahead of the actual purpose, which is slightly misplaced emphasis but does convey genuinely useful information.

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 single optional parameter with no output schema, the description covers return values and payment mechanics well. It stops short of covering the omitted-parameter default and invalid-input behavior, which are the remaining things an agent could need to call it correctly.

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 coverage is 100% and the tz property is documented with an example, so the baseline is 3. The description adds limited value by specifying 'any IANA timezone,' which tightens the accepted value domain beyond the schema's single example, but says nothing about default behavior when tz is omitted.

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 resource and its returned representations: 'Current time: UTC ISO string, unix timestamp and any IANA timezone.' An agent knows exactly what it gets back, though it does not distinguish itself from any sibling (which is acceptable for a trivially scoped utility).

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternatives named. The only usage-adjacent sentence, 'tools/call returns the live payment challenge,' concerns the payment flow rather than when to call this tool, so selection guidance is essentially implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources