QUOTEZ

Overview Schema Source Related Servers Score Discussions Admin

Get contract specification

symbol_info

Read-only

Retrieve the contract specification for a trading symbol, including tick value, spread, contract size, and margin currencies. Use this to check tradable details before placing orders.

Instructions

Return the contract specification for one instrument.

Digits and point size for rounding prices, current spread, minimum stop distance, tick value and size, contract size, the tradable volume range, and the base, profit and margin currencies. Field names are MetaTrader's own. An unknown or unavailable symbol returns a tool error naming the symbol. On the replay source the instrument is generated and the payload carries synthetic=true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	Yes	Instrument name exactly as list_symbols spells it.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Symbol name.
`point`	Yes	Value of one point, the smallest price step.
`digits`	Yes	Decimal places in a quoted price.
`source`	Yes	Data source that produced this specification.
`spread`	Yes	Current spread in points.
`synthetic`	Yes	True when the instrument is generated, not real.
`volume_max`	Yes	Largest tradable volume, in lots.
`volume_min`	Yes	Smallest tradable volume, in lots.
`description`	Yes	Human readable instrument name.
`volume_step`	Yes	Volume increment, in lots.
`spread_float`	Yes	True when the broker quotes a floating spread.
`currency_base`	Yes	Base currency of the instrument.
`currency_margin`	Yes	Currency the margin is charged in.
`currency_profit`	Yes	Currency the profit is denominated in.
`trade_tick_size`	Yes	Smallest price change, in price units.
`trade_tick_value`	Yes	Profit in the account currency from a one tick move on one lot.
`trade_stops_level`	Yes	Minimum distance in points between price and a stop or limit order.
`trade_freeze_level`	Yes	Distance in points within which orders are frozen and cannot be changed.
`trade_contract_size`	Yes	Units of the base asset in one lot.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the tool is safe to call without side effects. The description adds behavioral context: it lists the exact return fields (digits, spread, tick value, etc.), notes that unknown symbols cause a tool error, and mentions that on replay sources synthetic=true is added. This goes beyond annotations without contradicting them.

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?

The description is concise (three sentences) and front-loaded with the purpose. Each sentence adds relevant detail (return fields, naming, edge cases). Slightly verbose in listing fields could be trimmed, but it remains efficient.

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?

Given that there is no output schema but an output schema exists (context says 'Has output schema: true'), the description thoroughly lists return fields and covers the key edge case of unknown symbols. With annotations providing read-only guarantee, and one simple parameter, the description is complete enough for an agent to use correctly.

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?

Even though schema coverage is 100% and the single parameter 'symbol' has a description, the description adds value by indicating that symbol names must match list_symbols exactly and that unknown symbols trigger an error. This aids correct invocation.

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?

The description clearly states 'Return the contract specification for one instrument,' which identifies the action (return) and the resource (contract specification for one instrument). It distinguishes itself from siblings like 'list_symbols' (which lists symbols, not specifications) and 'get_quote' (which gets quotes) by focusing on static contract details.

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?

The description implies usage when needing instrument specifications (digits, spread, tick value, etc.) but does not explicitly state when to use this tool versus alternatives. It mentions that an unknown symbol returns a tool error, which is helpful context. No explicit exclusions or alternatives are given, but the context is clear.

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

Install Server