Skip to main content
Glama

SCRIPTMASTERLABS — Perpetual Roadmap

Get the roadmap x402 payment terms

perpetual_x402_contract
Read-onlyIdempotent

Free. x402 v2 payment terms for the paid HTTP endpoint GET /v1/roadmap/{symbol}: price, network, asset, payTo and header names. Payment is made over HTTP, not through this tool.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, so the safety profile is covered. The description adds real value beyond them: the call is free, no payment occurs through the tool, and payment happens over HTTP against a separate endpoint — a boundary an agent would otherwise get wrong.

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 short sentences with the cost answer ('Free.') front-loaded, then the resource, then the behavioral boundary. No filler and nothing repeated from the schema.

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?

With no output schema, the description usefully enumerates the returned fields, and the annotations cover the read-only profile. The only shortfall is the unexplained {symbol} path variable that appears in the described endpoint but has no corresponding input.

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 the baseline is 4; there is nothing for the description to disambiguate. One minor ambiguity remains: the referenced endpoint contains a {symbol} path segment, yet the tool accepts no symbol input, and the description does not explain how that is resolved.

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 (x402 v2 payment terms for GET /v1/roadmap/{symbol}) and enumerates what is returned: price, network, asset, payTo and header names. It is clearly not the data-fetching sibling, but it never explicitly names perpetual_preview or perpetual_status to draw the contrast.

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?

'Free' and 'Payment is made over HTTP, not through this tool' imply the usage context (fetch terms first, then pay out-of-band), but there is no explicit when-to-use statement and no named alternative to select instead. The guidance is inferable rather than stated.

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