Skip to main content
Glama

get_best_inference_provider

Recommends a cloud inference provider for a specified model and priority, so you can compare hosting options by cost, performance, or balanced needs.

Instructions

Recommend the best cloud inference provider for a model.

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

Input Schema

NameRequiredDescriptionDefault
modelYes
priorityNobalanced

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the recommendation uses live pricing/availability data, not whether results are deterministic or ranked, and not whether any credentials or provider accounts are required. 'Recommend' implies a read-only advisory call, but that is inference rather than stated fact.

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?

A single front-loaded sentence with zero filler and no repetition of the tool name. It is efficient, though its brevity is part of why key selection parameters go unexplained.

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

Completeness2/5

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

An output schema exists, so return structure need not be described. However, for a recommendation tool with no annotations and an undocumented 'priority' input, the definition leaves the agent unable to know how to influence or interpret the recommendation — a significant gap given the tool's decision-making role.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. 'model' is self-evident from its name, but 'priority' (default 'balanced') is completely opaque — no enumeration of accepted values such as cost, latency, or quality, and no explanation of what 'balanced' optimizes for. The description adds no meaning beyond the bare 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?

States a specific verb and resource: 'Recommend the best cloud inference provider' for a given model. The task is unambiguous, but the description offers no differentiation from the related sibling calculate_cloud_vs_local_breakeven, leaving the agent to infer whether provider selection and breakeven analysis overlap.

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 by the wording 'best ... provider for a model' — the agent can infer it should call this when choosing where to host a model. There are no explicit when-to-use or when-not-to-use conditions and no mention of the related breakeven tool as an alternative for cost comparisons.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.