Skip to main content
Glama

SCRIPTMASTERLABS — Perpetual Roadmap

Preview a roadmap run provenance

perpetual_preview
Read-onlyIdempotent

Free. Provenance preview of the current roadmap run for AMC or GME: data providers, cross-check, reference archive, input hash. Does not include the projection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "perpetual_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesThe symbol to preview: AMC or GME.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / symbol / description
      Added value: +"The symbol to preview: AMC or GME."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is read-only and idempotent. The description adds useful behavioral context by stating that it is free, listing what provenance data is included, and clarifying that the projection is excluded.

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?

The description is two tight sentences with the cost signal front-loaded and the scope, contents, and exclusion stated efficiently. Every sentence earns its place.

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 simple read-only preview with one enum parameter and no output schema, the description is complete enough. It identifies the resource, the allowed symbols, the returned provenance components, and the key exclusion.

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 description coverage is 100%, and the single symbol parameter is fully documented with an enum. The description reinforces the AMC/GME scope but adds no parameter meaning beyond the schema.

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 verb and resource: a provenance preview of the current roadmap run, scoped to AMC or GME. It also lists the included provenance components and explicitly excludes the projection, though it does not directly differentiate itself from sibling tools.

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?

The description implies usage by calling it a free provenance preview and noting that it does not include the projection. However, it does not explicitly say when to use this instead of perpetual_status or perpetual_x402_contract.

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