Skip to main content
Glama

Get RoutersUA store terms

routersua_get_store_policy
Read-onlyIdempotent

Return one RoutersUA information page as published (Ukrainian, Markdown-like text) with its page URL and the store's telephone, email, address and contacts page. Use it for questions about delivery cost, payment methods, returns and exchange, privacy or who runs the store; for ship and delivery dates use routersua_estimate_delivery, and for branches or lockers routersua_find_delivery_points. Choose topic delivery-and-payment for delivery cost and payment, returns-and-exchange for returns and exchange, privacy-policy for personal data, about for the store. Warranty terms per product are in the specifications of routersua_get_product.

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": {
      "topic": "<topic>"
    },
    "name": "routersua_get_store_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesdelivery-and-payment: delivery methods and cost, payment methods; returns-and-exchange; privacy-policy; about: the store and its contacts.

Output Schema

NameRequiredDescriptionDefault
urlYes
textYes
emailYes
titleYes
addressYes
telegramYes
telephoneYes
contacts_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by disclosing the response shape — a single page of published Ukrainian text plus URL and store contact fields — which tells the agent what kind of content to expect. It does not discuss truncation, caching, or failure modes, but those are minor given the annotations and an output schema.

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?

It is one dense paragraph that is front-loaded with purpose before routing guidance, and every clause carries routing or content information. The topic-to-enum sentence partially duplicates the earlier question-category list, which is the only real redundancy.

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

Completeness5/5

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

For a single-enum, read-only lookup with an output schema, the description covers purpose, applicable questions, explicit alternatives, and enum selection. There is no meaningful gap an agent would need filled before invoking it correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the single enum parameter is documented in the schema, so the baseline is 3. The description's topic-selection sentence largely restates the enum descriptions, adding only modest shading ("who runs the store", "personal data") rather than new syntax or edge-case behavior.

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 first sentence gives a specific verb and resource ("Return one RoutersUA information page as published") and adds format and payload details (Ukrainian, Markdown-like text, page URL, store contacts). It also names the siblings it is not — routersua_estimate_delivery, routersua_find_delivery_points, routersua_get_product — so an agent can route correctly without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact question categories this tool answers (delivery cost, payment, returns/exchange, privacy, who runs the store) and explicitly redirects ship dates to routersua_estimate_delivery, branches/lockers to routersua_find_delivery_points, and warranty terms to routersua_get_product. The mapping of each enum value to its topic is also given, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources