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

@opensmm/mcp-server

Official
by opensmm-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Compare provider offers

compare_offers
Read-onlyIdempotent

Compare social-media growth offers by platform and objective, showing price-sorted providers with quality metrics and total price for the requested quantity, excluding suspended providers.

Instructions

One offer per provider for a platform+objective, cheapest first, each with measured quality (orders, deliveredRatio, startLatencyMs) and the total price for the requested quantity (priced at the service minimum when quantity is omitted). SUSPENDED providers are excluded. Read-only.

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": {
      "platform": "<platform>",
      "objective": "<objective>"
    },
    "name": "compare_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesSocial platform of the service
quantityNoOrder quantity to price each offer for; defaults to each service's minimum
objectiveYesGrowth objective, e.g. 'members'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the trailing 'Read-only' is redundant, but the description contributes genuine behavior: exactly one offer per provider, cheapest-first ordering, exclusion of SUSPENDED providers, and the minimum-quantity pricing fallback. It does not say how many providers typically appear or what happens when no offers match.

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?

Three tight sentences with the core result shape front-loaded and the exclusion rule and read-only note following. The parenthetical listing of quality fields is dense but earns its place since there is no output schema.

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 usefully enumerates the returned fields (orders, deliveredRatio, startLatencyMs, total price) and the filtering/ordering rules, which is what an agent needs to interpret results. It stops short of describing empty-result or error behavior for a comparison tool that could plausibly return nothing.

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 coverage is 100%, so both required enums and the quantity default are already documented in the schema. The description restates the platform+objective combination and the quantity fallback without adding format, interaction, or edge-case meaning beyond what the schema provides.

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 operation on a specific resource: produce one offer per provider for a platform+objective, sorted cheapest first, with quality metrics and priced total. This aggregation scope implicitly separates it from single-service siblings like get_quote and search_services, though no sibling is named.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the pre-order comparison step, but the description never says when to use it versus get_quote or search_services, nor does it state prerequisites or exclusions beyond suspended providers being filtered out.

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