Skip to main content
Glama

list_llm_keys

Lists saved LLM provider keys with masked values, default status, and validity so you can choose an ID for tasks or schedules without exposing secrets.

Instructions

List the LLM provider keys saved in this workspace: id, name, provider, masked key (prefix + last 4), whether it is the default for its provider, and its status (valid, invalid or unchecked). Never returns a secret. Pass an id as llm_key_id to run_task or create_schedule. Keys are added at https://app.browsa.io/dashboard/llm-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": "list_llm_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it declares the workspace scope, guarantees no secret is ever returned, and specifies the masked key format (prefix + last 4) and the status domain (valid, invalid, unchecked). It does not discuss pagination, ordering, or behavior when the workspace has no keys, which are the remaining minor gaps for a list operation.

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?

The definition is front-loaded with the verb and resource, then the return fields, then the security guarantee, then the follow-on usage. Every sentence earns its place, and the field enumeration is justified because no output schema exists.

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?

For a zero-parameter list tool with no annotations and no output schema, the description supplies the return shape, the safety guarantee, and the downstream usage pattern. Nothing an agent needs in order to select or invoke this tool is missing.

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 zero parameters, so the baseline is 4 and there is nothing in the schema needing explanation. The mention of llm_key_id refers to a parameter of other tools, not this one, and is framed as such.

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 opens with a specific verb and resource ("List the LLM provider keys saved in this workspace") and enumerates exactly what comes back, so an agent knows precisely what this tool does. It does not explicitly contrast itself with sibling list tools such as list_models or list_identities, which keeps it 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 Guidelines4/5

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

It states a concrete follow-on use ("Pass an id as llm_key_id to run_task or create_schedule") and where keys originate, which gives the agent clear context for why and when to call it. There is no explicit when-not-to-use or named alternative list tool, so it stops short of full routing guidance.

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