Skip to main content
Glama

Create asset condition assessment

create_asset_condition_assessment

Record a point-in-time condition assessment against an asset. Requires asset_condition_assessments:write scope. Call list_assets first to resolve asset_id.

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": {
      "asset_id": "<asset_id>",
      "assessed_on": "<assessed_on>"
    },
    "name": "create_asset_condition_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFree-form notes
methodNoAssessment method
defectsNoStructured defect findings (JSON)
asset_idYesAsset ID (required) - resolve via list_assets
assessed_onYesAssessment date (YYYY-MM-DD, required; today or earlier)
assessor_idNoAssessor user ID - resolve via list_users
condition_scoreNoCondition score (0-100)
replacement_costNoCurrent replacement value / CRV at assessment time
update_purchase_costNoDefault OFF - omit unless the user explicitly asks to update/overwrite the asset's purchase cost, or says their org treats purchase cost as the current replacement value. Recording an assessment does NOT by itself change purchase cost. When true, overwrites assets.purchase_cost with this replacement_cost (CRV); the prior value is preserved on the assessment as previous_purchase_cost (read-only). Create-only and not reversible via update - when unsure, leave it off and ask.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / assessor_id / description
      Previous value: -"Assessor user ID"New value: +"Assessor user ID - resolve via list_users"
    • changedInput schema / properties / asset_id / description
      Previous value: -"Asset ID (required)"New value: +"Asset ID (required) - resolve via list_assets"
  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 / asset_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})$"
    • addedInput schema / properties / defects / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  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 / asset_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})$"
    • removedInput schema / properties / defects / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  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 / asset_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})$"
    • addedInput schema / properties / defects / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds the required write scope and the point-in-time nature of the record, which is useful, but says nothing about duplicate handling or how the purchase-cost overwrite path behaves beyond what the schema field already explains.

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 filler. The purpose is front-loaded and the prerequisite follows immediately.

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 9-parameter create with a nested defects object and no output schema, the description-plus-schema pairing covers what is needed to invoke it correctly. It relies entirely on the schema for the CRV/purchase-cost overwrite nuance, which is acceptable given the schema is fully described, but a one-line caution in the description would strengthen it.

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 coverage is 100%, so the schema already documents all 9 parameters, including enums, defaults, and the destructive update_purchase_cost behavior. The description adds only the list_assets resolution hint, which duplicates the asset_id schema text, so 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: "Record a point-in-time condition assessment against an asset." The phrase "point-in-time" plus "Record" signals an append-style create rather than an edit. It does not explicitly name update_asset_condition_assessment as the counterpart for later edits, so sibling differentiation is only partial.

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 concrete prerequisite workflow: "Call list_assets first to resolve asset_id," and states the required scope. It does not address when to use this versus update_asset_condition_assessment, but the usage context is clear enough to act on.

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