Skip to main content
Glama
UplinkSwitch MCP server

UplinkSwitch MCP server

Official
by uplinkswitch

list_models

Browse the UplinkSwitch catalog to find models and check price per million tokens, filtering by case-insensitive query or type without an API key.

Instructions

List the models on the UplinkSwitch catalog with their price per million tokens. Needs no API key. Filter by a case-insensitive query across the id, display name and developer, and optionally by type.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly models of this kind
limitNoHow many models to return
queryNoCase-insensitive text to match against the model id, display name or developer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that no API key is required and that results include per-million-token pricing, but it omits ordering, whether results are silently truncated at `limit`, and any rate-limit or total-count behavior — meaningful gaps for a list tool with zero annotation coverage.

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: the first front-loads the resource and payload, the second covers auth and filtering. Nothing is padded, and the most decision-relevant fact (no API key needed) appears early.

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?

For a simple read-only list tool with full schema coverage and no output schema, the description supplies enough: what is listed, what fields come back, and that auth is unnecessary. Adding result-ordering or truncation behavior would make it complete, but nothing essential is missing to invoke it correctly.

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 all three parameters are already documented in the schema, including the case-insensitive matching fields and the type enum. The description largely restates the schema's query semantics rather than adding new meaning such as how `limit` interacts with result totals or whether multiple words in `query` are ANDed.

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 and resource ("List the models on the UplinkSwitch catalog") and adds what the caller gets back ("with their price per million tokens"). It is clearly a catalog-enumeration tool, distinguishable in spirit from a single-model `model` fetch or `compare_prices`, but it never names an alternative, so it stops short of a 5.

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?

Implies usage via "Filter by a case-insensitive query ... and optionally by type", which tells the agent how to narrow results but not when to prefer this tool over `model` or `compare_prices`. There are no explicit when-not conditions and no statement of prerequisites or workflow context beyond "Needs no API key".

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