Skip to main content
Glama

update_agent

Update an existing agent by merging the provided fields. Use when changing instructions, model, tools, or skills.

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

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
modelNo
toolsNo
skillsNo
descriptionNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered structurally; the description adds genuine value with the word 'merging', signalling a partial update where unspecified fields are preserved. It stops short of the important ambiguities for a nested mutation: whether tools and skills are replaced wholesale or appended, and whether changes are reversible.

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?

Two short sentences, front-loaded with the action and the merge semantics before the usage cue. The second sentence mildly duplicates the property names but is brief enough not to be wasteful.

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?

For a seven-parameter mutation with a nested object, zero schema coverage, and no output schema, the definition is too thin — an agent cannot tell how the model object should be structured or whether list fields replace or merge. The merge hint is the only substantive detail beyond the annotations.

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% with seven parameters, one of them a nested object, so the description must carry the semantics — but it only names four fields that already appear as property keys. It adds no meaning about the required id, the shape of the model object, or per-field merge versus replace behavior for the array fields.

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 ('Update an existing agent') plus the mechanism ('merging the provided fields'), which is more informative than a bare name restatement. It does not explicitly contrast with create_agent or the other update_* siblings, so differentiation is left implicit.

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?

'Use when changing instructions, model, tools, or skills' gives a usable trigger condition, so an agent knows this is the mutation path for an existing agent. However, it offers no exclusions (e.g., when to prefer create_agent versus delete_agent) and simply re-lists four of the seven parameters as the use case.

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.

Resources