Skip to main content
Glama

Get one SMM panel

get_panel
Read-onlyIdempotent

One SMM panel's full profile on PanelCompare: trust and component scores with how much evidence backs them, uptime, features, payment methods, supply chain and provider meter, and its cheapest listing for each service it sells, each with the market median for comparison. Use the slug from search_panels.

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": {
      "slug": "<slug>"
    },
    "name": "get_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPanel slug, e.g. "justanotherpanel".
servicesNoHow many services to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 fully covered structurally. The description's added value is the shape of the payload (scores with evidence backing, per-service cheapest listing against a market median), which is useful but is return-content description rather than behavior. Nothing is said about error handling for an unknown slug, so with annotations carrying the behavioral load a 3 is right.

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?

The resource and scope are front-loaded in the first clause, followed by a dense but well-ordered enumeration of returned fields, then a short routing sentence. Every phrase carries information; the single long sentence is heavy but not padded.

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 must describe return values, and it does so thoroughly — scores, evidence weighting, uptime, features, payments, supply chain, and per-service pricing with medians. The remaining gaps are minor: no mention of behavior for an invalid slug and no note on payload size relative to the services cap.

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 description coverage is 100%, so the schema already defines both parameters and the baseline would be 3. The description adds meaning by explaining that each service entry is the cheapest listing with a market median for comparison, which clarifies what the 'services' count actually governs. It still does not mention the default of 40 or the 1–100 bound, but those live in the schema.

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 single, specific resource ('One SMM panel's full profile on PanelCompare') and enumerates its contents — trust/component scores, uptime, features, payment methods, supply chain, per-service cheapest listings. That is far more specific than a restatement of the name, and 'Use the slug from search_panels' implicitly separates it from the discovery sibling. The only gap is that the retrieval verb itself is implied rather than stated.

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?

It gives a clear prerequisite and routing rule: the slug must come from search_panels, which tells an agent this is the detail-fetch step after discovery. It does not state when *not* to use it (e.g. use compare_service_prices for cross-panel comparison), so no explicit exclusions are offered.

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