Skip to main content
Glama
UplinkSwitch MCP server

UplinkSwitch MCP server

Official
by uplinkswitch

model

Retrieve one model's full catalog entry without an API key, including context window, output limit, supported parameters, endpoints, and exact pricing for informed model comparison.

Instructions

Get one model's full catalog entry: context window, output limit, supported parameters, endpoints and exact pricing. Needs no API key.

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": {
      "id": "<id>"
    },
    "name": "model"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe model id, exactly as list_models returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: "Get" signals a read-only, side-effect-free call, and "Needs no API key" discloses the authentication requirement, which is genuinely useful operational context. It stops short of error behavior for an invalid id or any rate-limit notes.

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 short sentences with no filler; the core action and its output are front-loaded, and the auth note is a compact, useful addendum.

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 one-parameter read tool with no output schema, enumerating the returned fields in prose is exactly the right compensation, and the no-key note closes the auth question. Only edge-case behavior for a nonexistent model id is left unaddressed.

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 coverage is 100%, so the single id parameter is already fully documented in the schema, including the cross-reference to list_models. The description adds nothing about the parameter beyond what the schema states, so 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 states a specific verb and resource ("Get one model's full catalog entry") and enumerates the returned content: context window, output limit, supported parameters, endpoints and pricing. The phrase "one model" implicitly separates it from list_models, though the sibling is never named.

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 only implied: an agent can infer this is the lookup to use once it already has a model id, while list_models supplies ids. There is no explicit when-to-use statement, no exclusion, and no mention of what to do when the id is unknown.

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