Skip to main content
Glama

List the LLM providers for bring-your-own-key AI

qr_list_ai_providers
Read-onlyIdempotent

List the LLM providers the engine accepts for bring-your-own-key AI designs (POST /api/qr/ai/generate), with each provider id, its default model and the recommended model ids. Any model id your provider offers works; the list is a recommendation, not an allowlist. qr_generate_ai does not need this: it uses the managed path with our keys.

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": "qr_list_ai_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesHow many providers the engine lists.
providersYesThe providers, in the engine's order.
modelsNoteYesReminder that the model list is a recommendation, not an allowlist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact beyond them: the returned model ids are recommendations, not an allowlist, so any model the provider offers is acceptable. It also names the endpoint the list relates to.

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?

Purpose and scope come first, then the allowlist caveat, then the sibling routing note — a sensible front-loaded order with no filler sentences. The parenthetical API path is slightly technical clutter but does anchor where BYOK applies, so it roughly earns its place.

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?

An output schema exists, yet the description still summarizes the returned fields and, more importantly, clarifies their normative status, which schemas rarely convey. With zero parameters and full annotation coverage of the safety profile, an agent has everything needed to decide to call it and interpret the result.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline applies. The description instead spends its words on output shape and validity semantics, which is the right allocation for a zero-arg call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists LLM providers the engine accepts for bring-your-own-key designs, and enumerates what each entry contains (provider id, default model, recommended model ids). An agent can distinguish this from qr_generate_ai purely from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says qr_generate_ai does not need this because it uses the managed key path, which is real routing guidance against a named sibling. It only implies the positive case (call this when a user wants BYOK) rather than stating it as a condition, so it stops short of a full when/when-not pair.

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.