Skip to main content
Glama
Sign In

SCRIPTMASTERLABS — x402 Gateway

by com.scriptmasterlabs
OverviewDiscussionsAdmin

sml_xray_bars

Read-onlyIdempotent

OWNER-ONLY private feed for the Script Master Labs First Candle X-RAY app. Requires the owner access key; returns nothing without it. Not a public data product and not for agents: public agents should use regime_scan_ticker or precross_analyze for derived analysis.

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": {
      "access_key": "<access_key>",
      "symbols": "<symbols>",
      "months": "<months>"
    },
    "name": "sml_xray_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYesCalendar months, YYYY-MM.
symbolsYesUS stock/ETF tickers.
access_keyYesOwner credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: an owner access key is mandatory and the call returns nothing without it, which prevents an agent from misreading an empty result as a data gap. It stops short of describing rate limits or response shape.

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?

Three sentences, front-loaded with the ownership and credential constraint before the routing advice. There is mild redundancy between 'Not a public data product' and 'not for agents', but nothing that wastes an agent's reading time in a meaningful way.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining what comes back, and it only gestures at this via the app name 'X-RAY' and the ambiguous word 'bars'. The input, access and routing sides are complete; the return-value side is the remaining gap.

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?

Schema description coverage is 100%, so the baseline is 3. The description earns a bump by explaining the consequence of access_key ('returns nothing without it'), which the schema's terse 'Owner credential.' does not convey; symbols and months remain fully documented by the schema alone.

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 identifies a specific resource (First Candle X-RAY historical bar feed for Script Master Labs) and makes the access gate explicit. It separates itself from the analytical siblings by name, but never states in plain terms what a 'bar' payload contains (OHLCV candles, intraday vs daily), leaving the core output slightly implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both exclusions and destinations: 'not for agents' and 'public agents should use regime_scan_ticker or precross_analyze for derived analysis.' An agent reading this knows immediately when to skip the tool and exactly which siblings to pick instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SCRIPTMASTERLABS — x402 Gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources