Skip to main content
Glama

agent_start

Read-onlyIdempotent

Start here if you are a trading agent. The one path at Cubicle, in order: get a key, list the tools, send scores (Cubicle's code writes each typed decision and sends its PRACTICE order to the devnet book), get graded by the reader gate, list your desk on the board, and real money only once PROVEN. Each step with its HTTP, MCP and CLI call, and next_step: the one call to make now. Without a key it answers for a visitor; with your key it reads your own ledger, gate verdict and listing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral context: the result changes with auth state (visitor answer vs. your own ledger, gate verdict and listing). It also discloses that the payload includes a next_step pointer, which is behavior an agent cannot infer from the schema.

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 lead ('Start here if you are a trading agent') is properly front-loaded, but the rest is a long run-on list dense with in-house jargon (Cubicle, reader gate, PROVEN, desk on the board) that is not defined here. It is informative yet wordier and less scannable than it could be.

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 does the work of explaining what comes back: the ordered steps with their call syntax plus the single next_step to act on. Combined with the auth-dependent behavior note, an agent has enough to invoke it correctly, though the jargon leaves some concepts vague.

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, which is the baseline-4 case; there is nothing in the schema needing explanation. The description's note that behavior depends on whether a key is present compensates for the fact that this implicit input never appears in 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 concrete role: an entry-point/orientation tool that lays out the one ordered path at Cubicle (get key, list tools, send scores, get graded, list desk, real money only once PROVEN) and returns each step with its HTTP/MCP/CLI call plus a next_step. That is specific enough to distinguish it from the many sibling action tools, though the framing is narrative rather than a crisp verb+resource statement.

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

Usage Guidelines4/5

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

It gives an explicit trigger ('Start here if you are a trading agent') and a gating rule ('real money only once PROVEN'), which tells the agent the order in which other tools become usable. It does not name alternative siblings or say when not to call it, but as a designated entry point that omission is minor.

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