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

@opensmm/mcp-server

Official
by opensmm-protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List execution providers

list_providers
Read-onlyIdempotent

Lists connected execution providers with capabilities and gateway-measured quality metrics, including sample sizes, to help compare providers and choose one for an order.

Instructions

Pseudonymous list of connected execution providers with capabilities and gateway-measured quality metrics (sampleSize always shown; metric fields appear only with sufficient data). displayName is present only for providers that opted in to public listing.

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": "list_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 establish the safe read-only, idempotent profile, so the description is free to add real behavior, and it does: results are pseudonymous, sampleSize is always present, metric fields appear only with sufficient data, and displayName only for opted-in providers. The conditional-field rules are genuinely non-obvious and would otherwise surface as confusing nulls. It stops short of disclosing size, ordering, or pagination for an unfiltered list.

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?

Two sentences, both information-dense, with the core purpose stated first and the conditional-field caveats parenthetically attached to the metric mention. No filler, no restatement of the title, and every clause carries distinct signal.

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 input schema and no output schema, the description must carry the return-shape burden, and it does so well for field conditionality. It leaves ordering, result count, and pagination unstated, which matters for an unfiltered list an agent may scan to pick a provider.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The description correctly focuses on describing output characteristics rather than inventing input semantics.

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 names a specific resource and its contents: a pseudonymous listing of connected execution providers with capabilities and gateway-measured quality metrics. That is concrete enough to distinguish it from get_service or get_quote, though it never explicitly contrasts with the closest sibling, get_capabilities, which also concerns capabilities.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative among the ten siblings. The agent must infer that this is the discovery entry point before calling get_capabilities, get_service, or compare_offers, and nothing states whether an identifier from this list is required by those tools.

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