Skip to main content
Glama

update_llm

Modify an LLM's configuration including name, temperature, or max tokens by specifying the LLM ID and the fields to update.

Instructions

Update an LLM configuration. Only provide the fields you want to change.

Args: llm_id: The UUID of the LLM to update name: New display name temperature: New sampling temperature max_tokens: New maximum output tokens

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
llm_idYes
nameNo
temperatureNo
max_tokensNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description implies that unmentioned fields remain unchanged, but it does not detail side effects, permissions, or error conditions. Since no annotations are provided, the description carries the burden for transparency but is only partially sufficient.

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 description is short: two sentences plus an Args list. It front-loads the main action and usage hint, with no wasted words.

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?

The tool has an output schema (not shown), so return values are likely documented there. The description covers the essential: action, how to update, and parameters. It is fairly complete for a simple update tool, though prerequisites and error handling are omitted.

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 description adds meaning beyond the schema by explaining the usage pattern (only provide fields to change) and briefly describes each parameter in the Args list. With 0% schema description coverage, this provides necessary context.

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?

The description clearly states 'Update an LLM configuration' and specifies that only fields to change should be provided. This distinguishes it from creation (create_llm) and deletion (delete_llm) tools.

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?

The description advises to provide only fields to change, which is helpful. However, it lacks explicit guidance on when to use this tool vs alternatives like create_llm or delete_llm.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/anam-org/anam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server