Skip to main content
Glama

LastPing

by dev.lastping
OverviewDiscussionsAdmin

Update agent

update_agent
DestructiveIdempotent

Requires the write scope or higher. Updates an agent's name, description or slug by UUID with merge-patch semantics: supplied fields change, omitted ones keep their value. Renaming never changes the slug. A new slug has to be unique in the project; saved links, Terraform references and trace sources (service.name) naming the old slug then stop matching the agent unless they equal its name (case-insensitive), past traced runs included, and a slug equal to a source another agent receives takes that source's traces, past runs included. Attached monitors stay attached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAgent UUID (from register_agent or list_agents).
nameYesHuman-readable agent name, e.g. 'Deploy Bot'.
slugNoNew slug for the agent, e.g. 'reddit-bot': 3-50 characters, lowercase letters, digits and hyphens. Omitted: unchanged. After a change, references to the old slug (links, Terraform, trace sources and their past runs) stop matching this agent unless they equal its name (case-insensitive).
descriptionNoFree-text description of what this agent does. Omitted: unchanged. An explicit empty string clears it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Free-text description of what this agent does. Omit to leave the agent's current description unchanged — THIS IS THE DEFAULT AND SAFE CHOICE for a name-only rename. Pass an explicit empty string to clear an existing description back to none."New value: +"Free-text description of what this agent does. Omitted: unchanged. An explicit empty string clears it."
    • changedInput schema / properties / slug / description
      Previous value: -"New slug for the agent, e.g. 'reddit-bot': 3-50 characters, lowercase letters, digits and hyphens. Omit to keep the current slug, which is the default: pass it only when the person asks to change the slug. Saved links, Terraform references and trace sources that name the old slug stop matching this agent, unless they also equal its name (case-insensitive), past traced runs included; a slug equal to a source another agent receives by name or adoption takes that source's traces."New value: +"New slug for the agent, e.g. 'reddit-bot': 3-50 characters, lowercase letters, digits and hyphens. Omitted: unchanged. After a change, references to the old slug (links, Terraform, trace sources and their past runs) stop matching this agent unless they equal its name (case-insensitive)."
  2. Changed1 schema field changed
    • addedInput schema / properties / slug
      Added value: +{
+  "description": "New slug for the agent, e.g. 'reddit-bot': 3-50 characters, lowercase letters, digits and hyphens. Omit to keep the current slug, which is the default: pass it only when the person asks to change the slug. Saved links, Terraform references and trace sources that name the old slug stop matching this agent, unless they also equal its name (case-insensitive), past traced runs included; a slug equal to a source another agent receives by name or adoption takes that source's traces.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (destructiveHint, idempotentHint, openWorldHint), and the description adds substantial context beyond them: merge-patch semantics, that renaming never changes the slug, slug uniqueness constraints, the downstream impact on links/Terraform/trace sources and past runs, and that monitors stay attached. These are exactly the side effects an agent needs before invoking a destructive mutation.

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?

Front-loaded with the permission requirement and the action, and every clause carries information. The final slug-consequence sentence is dense and long, but none of its content is redundant with the schema.

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 destructive, idempotent mutation with no output schema, the description covers auth scope, update semantics, uniqueness constraints and all downstream side effects. Nothing an agent needs to call it safely 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining merge-patch behavior (supplied fields change, omitted ones keep their value) and the cross-parameter consequence of changing slug on the name field's matching semantics.

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 (Updates), resource (an agent), identified by UUID, and enumerates the mutable fields (name, description, slug). An agent can distinguish it from register_agent, get_agent and delete_agent without opening any schema.

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?

Gives a clear prerequisite ('Requires the write scope or higher') and describes update semantics, so the agent knows the context in which it applies. It does not, however, explicitly name an alternative tool or a when-not-to-use condition.

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

All LastPing toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources