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

@opensmm/mcp-server

Official
by opensmm-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search SMM services

search_services
Read-onlyIdempotent

Search sellable SMM services by text, platform, or objective and sort by price or measured quality. Suspended providers are excluded.

Instructions

Search the curated catalog of sellable SMM services by free text, platform and objective. Every offer carries providerRef (pseudonymous provider key) and quality (gateway-measured: orders, deliveredRatio, startLatencyMs). sort=price orders by normalized unit price, sort=quality by measured quality; default relevance keeps the catalog order. SUSPENDED providers are excluded.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoResult order: price (cheapest first), quality (best measured first), relevance (catalog order, default)
queryNoFree text, e.g. 'telegram members' or 'views'
platformNo
objectiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With readOnly/idempotent already in annotations, the description still adds real context: SUSPENDED providers are excluded, results carry providerRef and gateway-measured quality fields, and sort order semantics are spelled out. It does not cover result-count limits or pagination, which keeps it below a 5.

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 dense sentences, front-loaded with scope and followed by output shape and ordering. Nothing is redundant, though the middle sentence packs field-level detail that reads slightly like documentation rather than guidance.

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?

No output schema exists, and the description helpfully describes what each returned offer contains (providerRef and quality metrics). It is close to complete for a read-only search, with only pagination or result-limit behavior missing.

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

Parameters4/5

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

Schema coverage is 50%, with platform and objective enums undocumented in the schema; the description compensates by naming platform and objective as filter axes. It also adds meaning beyond the schema for sort by explaining that price means normalized unit price and quality means measured quality, which the enum text only summarizes.

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 opens with a specific verb and resource: search the curated catalog of sellable SMM services, and names the three filter axes (free text, platform, objective). It implicitly distinguishes itself from get_service and list_providers by framing it as a catalog search, but never names a sibling, so it falls short of full sibling differentiation.

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 implied through the filter list, and the default relevance ordering is stated, but the description never says when to search here versus compare_offers or list_providers, nor does it state any prerequisites. Adequate minimum-viable guidance with a clear gap around alternatives.

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