Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

place_market_order

Execute immediate buy or sell orders at current market prices for specified instruments, enabling real-time trading decisions through the Trading 212 platform.

Instructions

Place a market order to buy or sell at the current market price

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesThe ticker symbol of the instrument
quantityYesThe quantity to buy (positive) or sell (negative)
extendedHoursNoAllow execution outside regular trading hours (defaults to false)

Implementation Reference

  • The actual implementation of the place_market_order tool in the client.
    async placeMarketOrder(order: MarketOrderRequest): Promise<Order> {
      return this.request(
        '/equity/orders/market',
        {
          method: 'POST',
          body: JSON.stringify(order),
        },
        OrderSchema,
      );
    }
  • The request handler for the place_market_order tool.
    case 'place_market_order': {
      const validated = MarketOrderRequestSchema.parse(args);
      const order = await client.placeMarketOrder(validated);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(order, null, 2),
          },
        ],
      };
    }
  • src/index.ts:153-175 (registration)
    Registration of the place_market_order tool definition.
    {
      name: 'place_market_order',
      description: 'Place a market order to buy or sell at the current market price',
      inputSchema: {
        type: 'object',
        properties: {
          ticker: {
            type: 'string',
            description: 'The ticker symbol of the instrument',
          },
          quantity: {
            type: 'number',
            description: 'The quantity to buy (positive) or sell (negative)',
          },
          extendedHours: {
            type: 'boolean',
            description: 'Allow execution outside regular trading hours (defaults to false)',
            default: false,
          },
        },
        required: ['ticker', 'quantity'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a market order but doesn't cover critical aspects like execution guarantees, settlement time, fees, authentication requirements, rate limits, or what happens on failure. The description is insufficient for a financial transaction tool with no annotation support.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and doesn't include unnecessary elaboration or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a financial trading tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after order placement, return values, error conditions, or important behavioral context. The agent would lack critical information to use this tool effectively in a trading workflow.

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 parameters are fully documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema (ticker, quantity with sign convention, extendedHours default). Baseline score of 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('place a market order') and specifies the execution method ('buy or sell at the current market price'). It distinguishes from limit/stop orders by specifying 'market price' but doesn't explicitly differentiate from all sibling trading tools like 'place_limit_order' or 'place_stop_order' beyond the price mechanism.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'place_limit_order' or 'place_stop_order'. It doesn't mention prerequisites, trading contexts, or risk considerations that would help an agent choose between sibling order placement tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/enderekici/trading212-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server