Skip to main content
Glama

follow_quote

Read-onlyIdempotent

Quote following a trading model (from the STARTER plan, starter-20): checks the model is live and followable, validates the follower's sizing (fixed_notional usd, or proportional bps of their balance) and caps (max_notional_usd, max_open_positions, max_daily_loss_usd, markets the model trades), and shows what one mirror would be at the given balance. Creates nothing and moves nothing.

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": {
      "sizing": "<sizing>",
      "caps": "<caps>"
    },
    "name": "follow_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
capsYes{"max_notional_usd":100,"max_open_positions":3,"max_daily_loss_usd":40,"markets":["BTC"]}
modelNothe model's attribution from the models tool (or give script instead)
scriptNoinstead of a model: a PROVEN script's id from the strategies tool (scripts.proven); followed through the desk that runs it, only while the gate lists it PROVEN and the desk trades live
sizingYes{"kind":"fixed_notional","usd":50} or {"kind":"proportional","bps":200}
balance_usdNothe follower's balance, to show a mirror's size (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / model / description
      Previous value: -"the model's attribution from the models tool"New value: +"the model's attribution from the models tool (or give script instead)"
    • addedInput schema / properties / script
      Added value: +{
      +  "description": "instead of a model: a PROVEN script's id from the strategies tool (scripts.proven); followed through the desk that runs it, only while the gate lists it PROVEN and the desk trades live",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "model",
      -  "sizing",
      -  "caps"
      -]New value: +[
      +  "sizing",
      +  "caps"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive, and 'Creates nothing and moves nothing' largely restates that. The description goes further by disclosing side-effect-free validation behavior (liveness/followability check, sizing and cap validation) and that it returns a mirror preview, which are real behavioral facts 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.

Conciseness4/5

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

Front-loaded with the verb and resource, then the checks, then the outcome; the closing 'Creates nothing and moves nothing' is a useful, compact safety statement. The single long sentence with parenthetical plan metadata is slightly dense but nearly all of it earns its place.

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 five-parameter, side-effect-free quote tool with no output schema and fully documented schema, the description covers plan gating, validation behavior, the optional balance-driven preview, and the guarantee of no mutation. Only the shape of the returned quote is left vague.

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 description coverage is 100%, so the schema already documents all five parameters including the nested sizing/caps shapes. The description restates the sizing modes (fixed_notional usd vs proportional bps) and cap fields without adding syntax or formatting meaning beyond what the schema supplies, 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?

Opens with a specific verb+resource ('Quote following a trading model') and enumerates the checks performed (model live/followable, sizing, caps) and the output (a mirror preview at a given balance). It does not name a sibling such as 'follow' or 'strategy_quote' explicitly, though 'Creates nothing and moves nothing' implicitly separates it from an actual follow.

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?

Usage is implied rather than stated: the tool is clearly a pre-flight check before following, and the plan gate ('STARTER plan, starter-20') and model-vs-script choice are noted. There is no explicit 'use X to actually place the follow' or statement of when quoting is unnecessary.

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