Skip to main content
Glama

My compound growth plan

get_growth_plan
Read-only

The authenticated user's compound growth plan (set on /journal?tab=stats): current capital, today's profit target and daily stop, today's realized P/L, plus weekly/monthly targets and progress to the goal. CALL THIS BEFORE PROPOSING OR PLACING TRADES and follow it: aim for at most today's target, and STOP trading for the day once today's P/L reaches the target (status: target-hit) or drops to minus the daily stop (status: stop-hit). Read-only. Requires a personal SocialForex API token. Create one at /mt5 (section "Connect an AI assistant (MCP)") and add it to the MCP client as header Authorization: Bearer sfmcp_....

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover readOnlyHint/openWorldHint, but the description adds substantial context beyond them: the source path (/journal?tab=stats), the required personal SocialForex API token, how to create it, and the exact `Authorization: Bearer sfmcp_...` header format. It also names the status values that govern downstream trading behavior.

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?

Purpose is front-loaded, followed by the imperative usage rule, the read-only note, and auth setup in that order. The single paragraph is dense with clauses, but each sentence carries actionable information; only the auth-setup instructions add bulk that could be trimmed if the client already documents auth.

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?

With no output schema, the description must describe returns, and it does so specifically — capital, daily target/stop, realized P/L, weekly/monthly targets, progress, and status flags. Auth requirements are also covered, so nothing an agent needs to call it correctly is missing.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description spends its words on return semantics and auth instead of empty parameter space.

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?

States a specific verb+resource ('The authenticated user's compound growth plan') and enumerates the exact contents: current capital, today's profit target and daily stop, today's realized P/L, weekly/monthly targets, and goal progress. This clearly separates it from account-level siblings like get_my_mt5_account.

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?

Explicitly directs 'CALL THIS BEFORE PROPOSING OR PLACING TRADES,' which routes the agent ahead of place_mt5_order, and gives conditional follow-up rules tied to `status: target-hit` and `status: stop-hit`. Both when-to-use and the stopping condition are stated, leaving little to inference.

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.