Skip to main content
Glama

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

tick

[x402 paid: $0.001 USDC on Base] Exact server time: unix seconds + ISO 8601 UTC, one-liner for agents. 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": "tick"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the non-obvious traits: the tool is paid ($0.001 USDC on Base) and a tools/call invocation returns the live payment challenge rather than data, so the agent knows an unpaid first call will not produce a timestamp. It does not state whether payment is per-call or cached, nor what error responses look like beyond the challenge.

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 cost tag is front-loaded in brackets, followed by purpose and then the payment-challenge note, so an agent gets the critical facts immediately. The phrasing 'one-liner for agents' and 'live payment challenge' is slightly compressed, but nothing is padded or redundant.

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 time tool with no output schema, the description covers what an agent needs: the two output formats, the cost and network, and the fact that an unpaid call yields a payment challenge. Only the exact response envelope after payment is left unspecified, which is a minor gap given the stated formats.

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; the baseline for a parameterless tool applies. The description correctly adds no parameter noise and focuses on output and payment behavior instead.

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 resource and its return content: exact server time in unix seconds and ISO 8601 UTC, plus a note that it is a one-liner for agents. That is far more specific than a tautology on 'tick'. It stops short of distinguishing itself from the sibling 'time' tool, so it lands at 4 rather than 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 only implied: an agent infers it should call this when it needs a precise server timestamp. There is no explicit when-to-use, when-not-to-use, or reference to an alternative such as the sibling 'time' tool. The note that the call returns a live payment challenge adds useful context but is behavioral, not selection guidance.

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