Skip to main content
Glama

Update asset condition assessment

update_asset_condition_assessment
DestructiveIdempotent

Update an existing asset condition assessment by ID. Requires asset_condition_assessments:write scope. Note: the purchase-cost writeback is create-only and cannot be triggered by an update.

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

Input Schema

NameRequiredDescriptionDefault
idYesAssessment ID
notesNoFree-form notes
methodNoAssessment method
defectsNoStructured defect findings (JSON)
assessed_onNoAssessment date (YYYY-MM-DD, today or earlier)
assessor_idNoAssessor user ID - resolve via list_users
condition_scoreNoCondition score (0-100)
replacement_costNoCurrent replacement value / CRV

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assessor_id / description
      Previous value: -"Assessor user ID"New value: +"Assessor user ID - resolve via list_users"
  2. Changed4 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 / defects / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • 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. Changed4 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 / defects / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • 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. Changed4 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 / defects / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • 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.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description goes beyond them by disclosing the required auth scope and a non-obvious side effect (purchase-cost writeback is create-only and cannot be re-triggered here). It does not explain what 'destructive' means in practice — e.g. whether omitted fields are cleared — which is the one behavioral question left open.

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 tight clauses with zero filler: the action is front-loaded, followed by the prerequisite, followed by the caveat. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation with a nested object (defects) and no output schema, the description leaves the partial-vs-full update question unanswered, which is the main thing an agent needs before calling a tool flagged destructive. Auth scope and the cost caveat are covered well, so it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with all 8 parameters documented (including enum values and the list_users hint for assessor_id), so the schema carries the semantics. The description adds nothing about parameter behavior and only alludes to a field (purchase cost) that isn't even in the schema. Baseline 3 applies.

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 ... asset condition assessment) and names the lookup key (by ID), which cleanly separates it from get_asset_condition_assessment, create_asset_condition_assessment and delete_asset_condition_assessment. It does not explicitly distinguish itself from the analogous update_infrastructure_asset_inspection/update_asset_* siblings, but the resource is 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?

The write-scope requirement and the create-only purchase-cost note imply this is for modifying an already-existing assessment, but the description never says when to use it over create_* or whether it is a full replace versus a partial patch. Usage is inferable rather than stated.

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