Skip to main content
Glama

Update asset status

update_asset_status
DestructiveIdempotent

Update an existing asset status by ID. Requires asset_statuses:write scope. On the built-in Archived status (system_key archived) only name and description can change; it always shows red.

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_asset_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAsset status ID
nameNoStatus name
colorNoBadge color in the app: green, blue, amber or red. null = blue.
moduleNoMove the status to a workspace: facilities, infrastructure, or shared (both).
descriptionNoDescription

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / color
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "green",
      +        "blue",
      +        "amber",
      +        "red"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Badge color in the app: green, blue, amber or red. null = blue."
      +}
  2. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by naming the required scope (asset_statuses:write) and disclosing a genuine edge case: the built-in Archived status only allows name/description changes and is locked to red. Annotations declare destructiveHint=true and idempotentHint=true but say nothing about these restrictions, so the description carries real added weight. It does not explain what 'destructive' means in practice here, e.g. that moving a status across modules may orphan its asset assignments.

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?

Three short sentences, each earning its place: purpose, auth prerequisite, then the tricky edge case. Front-loaded and waste-free.

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?

For a 5-parameter update with full schema descriptions and no output schema, this covers purpose, scope requirement and the one non-obvious special case. Minor gap: no mention of whether the endpoint is a full replace or a partial patch (relevant since only id is required).

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; the description earns an extra point because it discloses a parameter-level constraint the schema omits – color and module are effectively immutable on the system Archived status, so passing them there is silently ineffective. That is exactly the kind of semantic the schema cannot express.

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 asset status by ID'), clearly distinguished from create_asset_status, delete_asset_status, get_asset_status and list_asset_statuses by the verb. It does not explicitly name a sibling, but the CRUD naming convention makes the scope unambiguous.

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?

Usage is implied by 'Update an existing' – an agent knows this is for modifying, not creating or deleting. However, there is no explicit when-to-use guidance versus alternatives, and no statement about whether assets already using the status are affected by renames or module moves.

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