Saymon RU Data API

pochta_delivery_time

Почта России: сроки доставки между индексами (в днях). $0.01 USDC

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": {
      "from_index": "<from_index>",
      "to_index": "<to_index>"
    },
    "name": "pochta_delivery_time"
  }
}

Input Schema

Name	Required	Default
`to_index`	Yes
`mail_type`	No	POSTAL_PARCEL
`from_index`	Yes
`mail_category`	No	ORDINARY

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 10, 2026

removedInput schema / properties / args

Removed value: -{
-  "additionalProperties": true,
-  "title": "Args",
-  "type": "object"
-}

removedInput schema / properties / extra

Removed value: -{
-  "additionalProperties": true,
-  "title": "Extra",
-  "type": "object"
-}

addedInput schema / properties / from_index

Added value: +{
+  "title": "From Index",
+  "type": "string"
+}

addedInput schema / properties / mail_category

Added value: +{
+  "default": "ORDINARY",
+  "title": "Mail Category",
+  "type": "string"
+}

addedInput schema / properties / mail_type

Added value: +{
+  "default": "POSTAL_PARCEL",
+  "title": "Mail Type",
+  "type": "string"
+}

addedInput schema / properties / to_index

Added value: +{
+  "title": "To Index",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "args",
-  "extra"
-]New value: +[
+  "from_index",
+  "to_index"
+]

changedInput schema / title

Previous value: -"wrapped_handlerArguments"New value: +"pochta_delivery_timeArguments"

AddedAug 23, 2026

TDQS

C2.4/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 full responsibility. It discloses the cost ($0.01 USDC), which is useful, but does not state that it is a read-only operation, what happens with invalid indexes, whether authentication is needed, or any rate limitations. The safety profile is largely undisclosed.

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 a single short sentence that leads with the purpose and includes the cost. It is efficient and free of fluff. However, it under-specifies important details, so while concise, it is not backed by supporting structure like parameter notes.

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

Completeness1/5

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

Given a 4-parameter tool with 0% schema coverage, no output schema, and no annotations, the description is severely insufficient. It omits parameter semantics, expected output, error handling, and any usage conditions. An agent would struggle to call this tool correctly without external knowledge.

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?

Schema description coverage is 0% and the description mentions none of the four parameters (from_index, to_index, mail_type, mail_category). It does not explain what these values represent or how to format them. The description fails to compensate for the missing schema documentation.

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 states a specific verb ('delivery times') and resource ('between indexes'), and mentions the unit ('in days'). It conveys the core function clearly and is distinct from siblings like pochta_tariff (tariffs) and pochta_track (tracking). However, it doesn't explicitly name alternatives or differentiate itself, so it falls short of a 5.

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 is given on when to use this tool compared to siblings like pochta_tariff or pochta_delivery. There are no exclusions, prerequisites, or suggested contexts. The description merely states what it does without any usage direction.

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

All Saymon RU Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?