Skip to main content
Glama

strategies

Read-onlyIdempotent

The strategies anyone can rent to run a Cubicle spot vault (today: accumulate, which buys a fixed amount of ETH or BTC on an interval up to a budget and never sells): what each does, its parameters, the venues and assets, the limits the vault itself enforces, the fee, how to rent it, and its honest status (not live with real funds yet). Beside them, scripts.proven: the cubicle.scripts the reader gate PROVED (their own trades beat random entries under the same exit, on discovery and on a later confirmation), each by its shape and its proof, never its rules; a script that is not PROVEN is never listed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/closed-world, but the description adds real behavior beyond them: the explicit status warning that strategies are 'not live with real funds yet', and the inclusion rule that a non-PROVEN script is never listed and proven scripts are described by shape and proof rather than by rules. What is missing is any hint about result size, ordering, or pagination for a listing call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope is front-loaded ('The strategies anyone can rent...'), but the whole definition is a single run-on sentence with nested parentheticals that packs two distinct subjects — the strategy catalog and scripts.proven — into one breath. Every clause carries information, yet splitting it into two sentences would cost nothing and improve scanability.

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?

There is no output schema, so the description must carry the return shape, and it largely does: per strategy it promises parameters, venues and assets, vault-enforced limits, fee, rental path, and status; for proven scripts it names the fields (shape, proof) and the gating evidence used. The exact structure of 'shape' and 'proof' remains abstract, which keeps it off a 5.

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, so the baseline of 4 applies. The schema description coverage is 100% and there is nothing for the description to disambiguate on the input side.

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 clear subject and enumerates what the reader gets: rentable Cubicle spot-vault strategies (today only 'accumulate', defined as buying a fixed amount of ETH or BTC on an interval up to a budget and never selling) plus a second section, scripts.proven. It never says 'returns' or 'lists' explicitly and does not distinguish it from lookalike siblings such as catalogue or plans, so it stops short of a 5.

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?

Use is implied rather than stated: the mention of 'how to rent it' and of the fee suggests this is the discovery step before renting, and the 'never a non-PROVEN script' clause implies a trust-oriented lookup. There is no explicit when-to-use or when-not-to-use and no named alternative tool, 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