Skip to main content
Glama

search_servers

Search dedicated, VPS, GPU and cloud server plans by specification, location, price and provider capability. Returns plans with on-site ServerSearcher URLs and affiliate checkout URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based
typeNoPlan types to include. Omit for all types.
minRamNoMinimum RAM in GB
cpuModelNoSubstring of the CPU model, e.g. "EPYC". `*` and `?` are glob wildcards: "EPYC*9004" matches "AMD EPYC 9004".
currencyNoISO 4217 currency codes to restrict prices to, e.g. ["USD","EUR"]
gpuModelNoExact GPU model name, e.g. "NVIDIA H100"
locationNoLocations: an ISO country code ("DE"), a country and city ("DE-frankfurt"), or a city id
maxPriceNoMaximum listed monthly price, in the listed currency
pageSizeNoResults per page, maximum 150
providerNoProvider slugs (e.g. "runpod") or internal provider ids — slugs are what URLs and get_provider_info use and are resolved for you.
diskTypesNoDisk types, e.g. NVMe, SSD, HDD
unmeteredNoOnly plans with unmetered bandwidth (no monthly transfer quota)
sortConfigNoSort order. The pricePer* keys rank by USD price per unit of RAM or CPU.priceAsc
minCpuCoresNoMinimum CPU cores
minGpuCountNoMinimum number of GPUs
hasTerraformNoOnly providers with an official or community Terraform provider
minBandwidthNoMinimum included bandwidth in TB per month
minPortSpeedNoMinimum network port speed in Mbps; matches either port
cloudServicesNoRestrict to providers offering any of these managed services, e.g. ["OBJECT_STORAGE","MANAGED_KUBERNETES"]
minCpuThreadsNoMinimum CPU threads
minCpuFrequencyNoMinimum CPU base frequency in GHz
minDiskCapacityNoMinimum capacity of a single disk, in GB

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / unmetered
      Added value: +{
      +  "description": "Only plans with unmetered bandwidth (no monthly transfer quota)",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / sortConfig / enum
      Previous value: -[
      -  "priceAsc",
      -  "priceDesc",
      -  "ramAsc",
      -  "ramDesc",
      -  "cpuAsc",
      -  "cpuDesc",
      -  "pricePerRam",
      -  "pricePerCpu",
      -  "pricePerRamCpu"
      -]New value: +[
      +  "priceAsc",
      +  "priceDesc",
      +  "ramAsc",
      +  "ramDesc",
      +  "cpuAsc",
      +  "cpuDesc",
      +  "diskDesc",
      +  "bandwidthDesc",
      +  "pricePerRam",
      +  "pricePerCpu",
      +  "pricePerRamCpu"
      +]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the return shape (plans with on-site ServerSearcher URLs and affiliate checkout URLs), which is genuinely useful behavioral context, but it omits pagination/result-cap behavior and any note that this is a read-only lookup with no side effects.

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?

Two well-formed sentences: the capability statement is front-loaded and the return note follows. No filler, though the second sentence leans slightly promotional ('affiliate checkout URLs') rather than operational.

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

Completeness3/5

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

For a 22-filter tool with no annotations and no output schema, the description covers the what and the basic return content but says nothing about pagination limits, empty-result behavior, or how the filter dimensions combine. Adequate as a minimum, but thin given the tool's complexity.

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 every one of the 22 parameters is already documented in the schema, including glob wildcards, location formats and sort keys. The description adds no parameter-level 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?

States a specific verb (Search) and resource (dedicated, VPS, GPU and cloud server plans) plus the filterable dimensions (specification, location, price, provider capability). It is clear on its own, but never names or contrasts itself with the siblings compare_providers or get_provider_info, so an agent must infer the boundary.

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 guidance, no mention of when not to use it, and no routing to the sibling tools. An agent cannot tell from the text whether it should search first or call get_provider_info/compare_providers, leaving the choice implicit.

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.