Skip to main content
Glama

SCRIPTMASTERLABS — Perpetual Roadmap

Check Perpetual Roadmap status

perpetual_status
Read-onlyIdempotent

Free. Service status and, per symbol (AMC, GME), whether a current roadmap run is available to buy, its last completed session and data freshness.

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_status"
  }
}

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?

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds value beyond them by disclosing that the call is free (no billing side effect) and that it returns data freshness and last completed session, which tells the agent results can be stale. It does not mention rate limits or refresh cadence, but that is a minor gap given annotation coverage.

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?

A single compact sentence, led by the high-value 'Free' qualifier and then the return payload, so the important information is front-loaded. The phrasing is dense and slightly awkward ('whether a current roadmap run is available to buy'), but nothing is wasted.

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 parameters, no output schema, and full annotation coverage, the description carries the burden of describing return values, which it does at reasonable detail: service status, per-symbol buy availability, last completed session, and freshness. The only missing element is a hint about how to act on that result relative to the sibling tools.

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 and the description correctly offers no parameter guidance, which is the appropriate baseline. The mention of specific symbols (AMC, GME) clarifies the shape of the returned per-symbol data rather than implying an input argument, so it does not mislead.

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 the exact payload: overall service status plus, per symbol (AMC, GME), whether a current roadmap run is buyable, its last completed session, and data freshness. That is concrete enough that an agent knows what it will get back. It does not, however, contrast itself with perpetual_preview or perpetual_x402_contract, so sibling differentiation is absent.

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: the 'Free' prefix and the availability field suggest this is the no-cost pre-check to run before a paid preview or contract call, but the description never states when to use this instead of a sibling. There are no exclusions or preconditions, so the agent must infer the routing.

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