@ethioviral/mcp

Get one SMM order

get_smm_order

Retrieve current status and real delivery progress for an SMM order, showing start count, delivered quantity, and remaining items.

Instructions

Status and real delivery progress (start count, delivered so far, remaining) for an SMM order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orderId": "<orderId>"
    },
    "name": "get_smm_order"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 16, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation by stating it returns status and progress, but it does not explicitly state that it has no side effects, nor does it mention error behavior or permissions. Minimal disclosure.

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?

A single concise sentence that front-loads the key information. No wasted words or filler.

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

Completeness3/5

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

For a simple get operation with one parameter and no output schema, the description gives the essential information about what is returned (status and progress). However, it does not describe the exact structure or fields of the response, nor does it mention any error conditions. Adequate for a straightforward lookup but lacks detail.

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

Parameters1/5

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

The input schema has a single required parameter orderId with no description. The tool description does not explain what orderId refers to or any constraints beyond the schema's minLength 1. With 0% schema description coverage, the description adds no value to the parameter meaning.

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 tool returns status and real delivery progress (start count, delivered so far, remaining) for an SMM order. It is specific about the resource and the data returned. However, it does not explicitly differentiate it from sibling tools like get_order or get_premium_delivery, relying on the name for that.

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?

No guidance on when to use this tool versus alternatives. It does not mention that this is for SMM orders specifically or contrast with get_order or get_premium_order. The agent must infer usage from the name alone.

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