Skip to main content
Glama

Theme Journey Trade Vehicle

theme_journey_trade_vehicle
Destructive

Needs your api_key (register_agent, no key needed). PLACE one crypto board vehicle with the signed-in user's OWN money through the routed plan: it fills on its best venue (DEX via their own trading wallet, the order book from their balance, or their own exchange). A vehicle no venue of theirs can settle is said so — nothing is forced and nothing is paid from platform funds. Call after theme_journey_route_vehicle and confirm_action. (needs your linked account's key)

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": {
      "api_key": "<api_key>",
      "symbol": "<symbol>",
      "usdc_amount": "<usdc_amount>"
    },
    "name": "theme_journey_trade_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesthe board symbol
api_keyYesYour api_key from register_agent
usdc_amountYesticket size in USD from the user's own balance (their USDT spends 1:1)
conversation_idNoconversation_id returned by an earlier theme_journey_* call (keeps an anonymous visitor's interests and basket together until they register).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive=true and non-idempotent, but the description adds real behavioral context: it spends the user's OWN money, routes to their best venue, and will refuse (rather than force) a vehicle no venue can settle with no platform funds involved. This clarifies the failure semantics and money source well beyond the annotations.

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 core intent is present but the api_key requirement is stated twice (opening parenthetical and trailing parenthetical), and jargon like 'board vehicle' and 'routed plan' add density without clarity. Front-loading the api_key note before the actual action is slightly awkward.

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?

For a destructive, non-idempotent mutation with no output schema, the description covers money source, venue routing, refusal behavior, and prerequisites. It's essentially complete for a correct-invocation decision, missing only explicit return/callback expectations.

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%, so the schema already documents all four parameters (symbol, api_key, usdc_amount, conversation_id). The description only reinforces the api_key requirement and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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 ('PLACE') and resource ('one crypto board vehicle') with the execution scope made explicit. It is distinguishable from theme_journey_route_vehicle (routing) and theme_journey_trade, though the term 'vehicle' is jargon that requires inferring it means a trade order.

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?

Explicitly says 'Call after theme_journey_route_vehicle and confirm_action,' giving a clear prerequisite sequence. It lacks an explicit when-not or a direct contrast against the sibling theme_journey_trade, which keeps it from a 5.

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