Skip to main content
Glama

script_catalogue

Read-onlyIdempotent

The cubicle.script catalogue, read from the runner: every function with its signature, what it returns and its Pine equivalent (ta.ema for ema; high(n) is ta.highest(high, n)[1], the bars before this one), the series, built-ins and truths a gate can read, the order kinds, where an order can fill, the fill models, the draw kinds, the timeframes and the budget. Pass name to keep only the names that contain it. Free.

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

Input Schema

NameRequiredDescriptionDefault
nameNokeep only the entries whose name (or Pine name) contains this, such as atr or ta.rsi

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by noting the data is 'read from the runner' (authoritative source) and that the call is 'Free' (no budget consumed) – a meaningful cost disclosure absent from annotations. It says nothing about result size, ordering, or truncation for a catalogue described as 'every function'.

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?

Front-loaded with identity and purpose in the first clause, and every clause carries content. However, it is one long run-on sentence whose long enumeration of catalogue categories would scan faster as a list, and the filter sentence sits awkwardly after the inventory.

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 carries the burden of describing return values, and it does so by enumerating the catalogue's sections, which is enough for an agent to know what to expect. The missing piece is shape/scale of the response (how entries are keyed, whether signatures are strings or objects), but overall it is adequate for a zero-required-param reference lookup.

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 coverage is 100%, and the schema already documents `name` as a substring filter matching the name or Pine name with examples (atr, ta.rsi). The description's 'keep only the names that contain it' restates the schema rather than adding new meaning. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb+resource: it returns the cubicle.script catalogue read from the runner, and enumerates the categories it contains (functions with signatures and returns, Pine equivalents, series, built-ins, order kinds, fill models, draw kinds, timeframes, budget). An agent knows exactly what reference data it gets, though it never contrasts itself with the sibling 'catalogue' or with script_explain.

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?

No explicit when-to-use or when-not guidance is given, but the enumerated content implies the use case: look up a function's signature/return/Pine mapping before writing or explaining a script. The only operational guidance is 'Pass `name` to keep only the names that contain it. Free.'

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