Skip to main content
Glama

ozon_order_fbs_country_set

Update the product country in an FBS posting by providing the posting number, product ID, and country ISO code to keep order data accurate.

Instructions

Set the product country in a posting (указать страну).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYes
country_isoYes
posting_numberYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.5.2

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. 'Set' implies mutation, but the description does not state whether the operation overwrites an existing country, whether it is reversible, what valid country_iso values are, or what side effects or errors may occur.

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 sentence is short and the verb is front-loaded, but the parenthetical Russian translation '(указать страну)' adds redundant noise without new information. It is concise but not maximally efficient.

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 mutation tool with three required parameters, no output schema, and no annotations, the description is too sparse. It does not mention related operations like country lists or restrictions, expected return values, or any operational context an agent would need to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only loosely references 'product country' and 'posting'. It does not explain the format or meaning of posting_number, product_id, or country_iso, nor any validation rules or allowed values.

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 uses a specific verb ('Set') and identifies a clear resource: the product country within a posting. This clearly separates it from the sibling list operation, though it does not explicitly name or contrast any alternative tool.

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 ozon_order_fbs_country_list or ozon_order_fbs_restrictions. There is no mention of prerequisites, posting state requirements, or when this action is applicable.

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/DeviceIngineering/ozon-mcp-server'

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