Skip to main content
Glama

Create asset betterment

create_asset_betterment

Record capital work that ALREADY extended a facility asset's life - an elevator modernization, a boiler retube, a major component replacement. Required: asset_id and occurred_on; capitalized_amount and added_life_years are optional and may be 0. The asset's net book value and remaining life re-base from occurred_on, and its purchase_date is NEVER changed - if a user asks to change an in-service date to reflect an overhaul, record this instead and say why. Use asset_lifecycle_events for work expected in future; use a condition assessment for what someone observed. Call list_assets first to resolve asset_id. Requires asset_betterments: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": {
      "asset_id": "<asset_id>",
      "occurred_on": "<occurred_on>"
    },
    "name": "create_asset_betterment"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYesAsset the capital work was performed on (required) - resolve via list_assets
project_idNoThe project that delivered it - resolve via list_projects
descriptionNoWhat was actually done
occurred_onYesDate the work went into service, YYYY-MM-DD (required). Not the invoice date - this is the date its value begins depreciating from.
asset_cost_idNoThe asset cost row holding the spend, so the money is not double-entered - resolve via list_asset_costs
work_order_idNoThe work order that delivered it - resolve via list_work_orders
added_life_yearsNoExtra service life the work bought, in years. Optional.
capitalized_amountNoAmount added to the asset value, in the organization currency (call get_organization_settings for currency_code). Optional, defaults to 0.
asset_lifecycle_event_idNoThe lifecycle strategy event this executed, if any - resolve via list_asset_lifecycle_events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / added_life_years / description
      Previous value: -"Extra service life the work bought, in years. Required unless capitalized_amount is given."New value: +"Extra service life the work bought, in years. Optional."
    • changedInput schema / properties / added_life_years / minimum
      Previous value: -0.1New value: +0
    • changedInput schema / properties / capitalized_amount / description
      Previous value: -"Amount added to the asset value, in the organization currency (call get_organization_settings for currency_code). Required unless added_life_years is given."New value: +"Amount added to the asset value, in the organization currency (call get_organization_settings for currency_code). Optional, defaults to 0."
  2. Changed5 schema fields changed
    • changedInput schema / properties / asset_cost_id / description
      Previous value: -"The asset cost row holding the spend, so the money is not double-entered"New value: +"The asset cost row holding the spend, so the money is not double-entered - resolve via list_asset_costs"
    • changedInput schema / properties / asset_id / description
      Previous value: -"Asset the capital work was performed on (required)"New value: +"Asset the capital work was performed on (required) - resolve via list_assets"
    • changedInput schema / properties / asset_lifecycle_event_id / description
      Previous value: -"The lifecycle strategy event this executed, if any"New value: +"The lifecycle strategy event this executed, if any - resolve via list_asset_lifecycle_events"
    • changedInput schema / properties / project_id / description
      Previous value: -"The project that delivered it"New value: +"The project that delivered it - resolve via list_projects"
    • changedInput schema / properties / work_order_id / description
      Previous value: -"The work order that delivered it"New value: +"The work order that delivered it - resolve via list_work_orders"
  3. Changed7 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_cost_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 / 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 / asset_lifecycle_event_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 / project_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 / work_order_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})$"
  4. Changed7 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_cost_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 / 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 / asset_lifecycle_event_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 / project_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 / work_order_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})$"
  5. Changed7 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_cost_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 / 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 / asset_lifecycle_event_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 / project_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 / work_order_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})$"
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the write/safety profile (readOnlyHint=false, destructiveHint=false), and the description goes further by disclosing the downstream effects: net book value and remaining life re-base from occurred_on, while purchase_date is never modified. It also states the required write scope, though it does not mention idempotency or duplicate-submission behavior.

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?

Front-loads the core definition and the 'ALREADY' emphasis, then moves through requirements, side effects, alternatives, and scope in a tight sequence. Every sentence carries distinct information; no filler or repetition of the schema.

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 mutation with no output schema, it covers the critical gaps: what it changes downstream, what it never changes, prerequisites, alternatives, and auth scope. Only returning-shape and duplicate-handling details are absent, which is a minor gap given full annotation coverage.

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 schema already carries parameter meaning and the baseline is 3. The description still adds value by flagging required vs optional fields and clarifying that capitalized_amount and added_life_years may legitimately be 0, plus the occurred_on re-basing 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 and resource (record capital work that extended an asset's life) and grounds it with three concrete examples (elevator modernization, boiler retube, component replacement). It also names the two nearest neighbours (asset_lifecycle_events, condition assessment) so the agent can separate this from look-alike writes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (work ALREADY completed) versus when-not (future work → asset_lifecycle_events; observations → condition assessment), plus a prerequisite (call list_assets first to resolve asset_id) and an explicit redirect for the in-service-date misuse case.

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