Skip to main content
Glama

Search SKUs

search_skus
Read-onlyIdempotent

Find VPS plans, GPU instances or LLM models by name/id substring, category (vps|gpu|llm) and provider. Active SKUs on the provider's public price page or product API by default (listing filter). Returns each match's current list price, listing_status, unit and currency, verified_at, stale flag and source_url. Read-only; reads the ledger's own daily archive, nothing is fetched live.

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_skus"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows, 1 to 200
queryNoSubstring of the SKU name or id, e.g. 'h100' or 'claude-sonnet'. Empty matches every active SKU, ordered by category, provider, plan.
listingNoListing filter. current (default) = on the provider's public price page or product API; catalog_only = only in an order catalog, not on the public page; vanished = was listed, now missing; unknown = no public page to check against; all = everything. Every row carries listing_status.current
categoryNovps, gpu or llm
providerNoProvider slug, e.g. vultr, ovhcloud, openai

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description nonetheless adds real value beyond them: it discloses the data provenance ('reads the ledger's own daily archive, nothing is fetched live'), which tells the agent results may lag live pricing, and it enumerates the returned fields including a stale flag and source_url.

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?

Four compact sentences, front-loaded with what is searchable, then default filtering, then return shape, then provenance. No filler, though the parenthetical '(listing filter)' is slightly redundant with the schema's own parameter description.

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

Completeness5/5

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

For a zero-required-parameter search tool with no output schema, the definition covers search surface, default filter semantics, returned fields, and data freshness in one place. An agent has everything needed to call it correctly and interpret the results.

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 100%, so the schema already documents every parameter including the listing enum and its default. The description restates substring matching on name or id and the vps|gpu|llm category set but adds no syntax, formatting, or edge-case meaning beyond that, so the baseline 3 applies.

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 gives a specific verb ('Find') and precise resource scope ('VPS plans, GPU instances or LLM models') plus the matching dimensions (name/id substring, category, provider). It is clear enough that an agent would not confuse it with a single-price lookup, though it never names a sibling tool explicitly.

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 rather than stated: the default 'listing=current' behavior tells the agent what it gets by default, and 'Empty matches every active SKU' hints at broad-listing use. There is no explicit when-to-use guidance, no statement of when to prefer this over get_price, vps_plans, or cheapest_for_spec, and no exclusions.

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