Skip to main content
Glama

Update infrastructure asset inspection

update_infrastructure_asset_inspection
DestructiveIdempotent

Update an existing infrastructure asset inspection by ID. Requires infrastructure_asset_inspections:write scope.

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

Input Schema

NameRequiredDescriptionDefault
idYesInspection ID
notesNoNotes
methodNoInspection method
defectsNoDefect observations
attachmentsNoAttachment URLs/paths
inspector_idNoInspector user ID - resolve via list_users
condition_scoreNoCondition score
inspection_dateNoInspection date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / inspector_id / description
      Previous value: -"Inspector user ID"New value: +"Inspector 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.5/5.0
Behavior3/5

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

The description adds the required 'infrastructure_asset_inspections:write' scope, which annotations do not express. However, annotations flag destructiveHint=true while the description never explains what is destructive — e.g. whether omitted fields are cleared (full replace vs patch) and whether nested 'defects' data is overwritten.

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?

Two short sentences, zero repetition of the title beyond what is needed, and the operation plus precondition are front-loaded. Nothing to trim.

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 a destructive, idempotent mutation with 8 parameters, a nested object and no output schema, the description is missing the one thing an agent can't infer: partial-update semantics and the consequence of the destructive hint. The scope requirement is a useful addition, but the mutation behavior remains underspecified.

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% and every parameter (including the defects map, attachments, condition_score bounds and the 'resolve via list_users' hint on inspector_id) is already documented in the schema. The description adds nothing about parameters beyond 'by ID', so the baseline of 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?

Clear specific verb + resource ('Update an existing infrastructure asset inspection') scoped by ID. It is distinguishable from create_infrastructure_asset_inspection and delete_infrastructure_asset_inspection, but does not explicitly contrast with update_infrastructure_asset or sibling update_* 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?

'Update an existing ... by ID' implies the record must already exist and that get_infrastructure_asset_inspection/list_infrastructure_asset_inspections would supply the ID, but there is no explicit when-to-use/when-not guidance or named alternative.

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