Skip to main content
Glama

Backtest360

by com.backtest360

get_me

The configured API key's permissions, limits, and current usage.

    Cheap. Call early in a session — before planning work — to learn what
    this key can do instead of discovering limits through failed calls.

    Returns:
        ``scopes``: the permission scopes the key carries. ``limits``:
        requests per minute and per day, max concurrent requests, and the
        per-run bar cap (null when uncapped). ``usage``: current
        consumption against those limits, with reset countdowns in
        seconds. ``capabilities``: feature flags such as server-side data
        fetch and the full metric set. A small fixed-shape record,
        returned as the engine sent it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior4/5

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

The description details the return structure (scopes, limits, usage, capabilities) and notes it's a 'small fixed-shape record' returned as sent. While it implies read-only behavior, it doesn't explicitly state non-destructiveness, but the cost indication ('Cheap') provides some transparency.

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 concise (three sentences) and front-loaded with the core purpose. Every sentence provides unique information: purpose, usage advice, and return field details.

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?

Given no parameters, the description fully covers what the agent needs: purpose, when to call, and the exact fields returned. The output schema existence further supports complete context.

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?

With zero parameters and 100% schema coverage, the description does not need to explain inputs. It uses the space to clarify the output structure, adding value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'the configured API key's permissions, limits, and current usage.' This is a specific verb-resource pair, and it distinguishes itself from sibling tools like get_quote or engine_info by focusing on authentication context.

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 explicitly advises to 'call early in a session — before planning work' to avoid failed calls, providing clear when-to-use guidance. No alternatives or exclusions are needed due to the tool's unique role.

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

All Backtest360 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Every tool targets a distinct operation or resource: backtesting, comparison, macro data, reference catalogs, etc. Even similar tools like run_backtest and compare_backtests are clearly differentiated by purpose and inputs.

Naming Consistency4/5

Overall consistent verb_noun pattern in snake_case, with a few exceptions like engine_info (noun_noun) and export_backtest (verb_noun but less common verb). The pattern is predictable and aids agent selection.

Tool Count4/5

20 tools is slightly above the ideal range but justified by the breadth of the platform (backtesting, data retrieval, reference, export). Each tool serves a clear purpose without redundancy.

Completeness4/5

Covers the full backtesting lifecycle: strategy validation, data sourcing, backtesting, comparison, export, and reference lookups. Minor gaps exist (e.g., no explicit strategy persistence), but the core workflow is complete.

Resources