Skip to main content
Glama

chromium-release

Chromium stable release tracker. No input: the current stable Chrome version and its release start time, fetched live from the official version history API, with days and hours since release. Price: $0.01 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "chromium-release"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/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 so: it discloses the data source (official version history API, live), the cost ($0.01 per call in USDC on Base mainnet over x402), and the failure behavior (unpaid calls return HTTP 402 with machine-readable payment terms). Cost, provenance, and error semantics are exactly the traits an agent needs before calling a paid endpoint.

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?

Three sentences in a deliberate order: what it returns, then data source and freshness, then payment mechanics. Every sentence adds information an agent needs, and the key result is front-loaded.

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 no-parameter, no-output-schema tool, the description covers return values, data provenance, freshness metric, price, payment rail, and the 402 error path. Nothing an agent needs to call it correctly or budget for it is missing.

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?

Zero parameters, so the baseline is 4, and the description reinforces this by explicitly stating 'No input', confirming the empty schema is intentional rather than truncated. No further parameter meaning is possible.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Chromium stable release) and exactly what is returned: the current stable Chrome version, its release start time, and days/hours since release. The verb-equivalent is precise ('fetched live from the official version history API'), so an agent knows this is a live lookup rather than a static table.

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?

'No input' makes the invocation condition unmistakable and implies use whenever an agent needs the current stable Chrome version or its release age. It stops short of naming alternatives or exclusions (e.g., when to prefer a different version source), so it lacks the explicit when-not routing of a 5.

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