submit_orderОтправляет все готовые ссылки заказа вебмастерам. Вызывать только после показа данных и явного подтверждения пользователя.
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | ||
| confirmed | Yes | ||
| idempotency_key | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds context that the tool sends links to webmasters and requires user confirmation, which is useful behavioral information beyond the annotations. It does not contradict any annotation, and the added precondition improves transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences, front-loaded with the action and followed by a clear condition. Every word earns its place, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and annotations covering idempotency and non-destructiveness, the description is sufficiently complete. It clearly states what the tool does and when to call it. Minor gaps exist (e.g., what 'ready links' means), but the overall context is adequate for a straightforward tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain any of the three parameters. While the schema itself includes types and constraints (e.g., confirmed is const true), the description does not add meaning or clarify the purpose of order_id or idempotency_key beyond the schema. The description mentions 'explicit user confirmation,' which aligns with the confirmed parameter, but that is minimal compensation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action: 'Sends all ready links of the order to webmasters.' This distinguishes it from sibling tools like submit_link, which likely handles individual links. The verb 'sends' and the resource 'all ready links of the order' make the purpose explicit and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear condition for use: 'Call only after showing data and explicit user confirmation.' This tells the agent when it is appropriate to invoke the tool. However, it does not mention alternatives or when not to use it in favor of another tool, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but a few pairs (check_registration vs get_account_profile, submit_link vs submit_order) overlap in scope. Descriptions clarify the differences (single vs bulk, status vs full profile), so confusion is limited.
All tool names follow a consistent verb_noun pattern in snake_case (begin_registration, list_orders, update_link_draft). The only slight deviation is 'bulk_update_order_draft' with the 'bulk' modifier, but it still fits the overall pattern.
14 tools is well within the ideal range for a specialized service covering registration, orders, links, tariffs, and checkout. Each tool serves a distinct function without unnecessary bloat.
The core workflow (register, browse tariffs, manage order drafts, submit links) is well covered. Minor gaps like lack of explicit order creation or deletion are likely handled externally or via the checkout process, so agents can still complete key tasks.