Skip to main content
Glama
Sign In
@opensmm/mcp-server

@opensmm/mcp-server

Official
by opensmm-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a price quote

get_quote
Read-onlyIdempotent

Price a social-media service for a specified quantity and optional target link, returning an expiring quote with the total amount required before order creation.

Instructions

Price a service for a quantity (and optionally the target link). Returns an expiring quote with the total amount. A quote is MANDATORY before create_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": {
      "serviceId": "<serviceId>",
      "quantity": "<quantity>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoTarget URL/identifier, e.g. https://t.me/channel
quantityYes
serviceIdYes
parametersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds genuinely new behavioral facts: the returned quote expires and carries a total amount, and the call is a required gate before order creation. It does not say how long the quote lasts or what happens if an expired quote is used downstream.

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?

Three short sentences with zero filler, and the core purpose plus return value are front-loaded before the ordering constraint. The capitalization of MANDATORY is a deliberate, well-placed emphasis rather than noise.

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

Completeness4/5

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

With no output schema, the description correctly summarizes the return value (expiring quote with total amount), and the ordering constraint is stated. The remaining gap is the nested "parameters" input, which an agent cannot confidently populate from either schema or description.

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 only 25%, so the description should compensate more than it does; it clarifies that link is optional and that quantity drives pricing, but never explains the nested "parameters" object or the serviceId format. It adds partial meaning over the schema but leaves the most ambiguous parameter undocumented.

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 pairs a concrete verb and resource ("Price a service") with the inputs it needs (quantity, optional link) and states the output (an expiring quote with a total amount). It distinguishes itself from create_order by declaring the quote prerequisite, though it does not differentiate from other pricing-adjacent siblings such as compare_offers or get_service.

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

Usage Guidelines4/5

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

"A quote is MANDATORY before create_order" is an explicit, actionable when-to-use rule tied to a named sibling. It lacks any when-not-to-use guidance or comparison against compare_offers, which also appears to be a pricing-related option.

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

Deploy Server

Other Tools