Skip to main content
Glama

List infrastructure asset costs

list_infrastructure_asset_costs
Read-onlyIdempotent

List cost rows for infrastructure features. Filter by feature, work order, vendor, category, or cost date range. Amounts are bare numbers with no currency: call get_organization_settings for currency_code before stating one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_infrastructure_asset_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: all pages fetched automatically)
categoryNoFilter by cost category
per_pageNoItems per page (default: 1000, max: 1000). All pages are fetched automatically.
vendor_idNoFilter by vendor ID - resolve via list_vendors
feature_idNoFilter by infrastructure feature ID - resolve via list_infrastructure_assets
cost_date_toNoCosts on/before this date (YYYY-MM-DD)
work_order_idNoFilter by work order ID - resolve via list_work_orders
cost_date_fromNoCosts on/after this date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / feature_id / description
      Previous value: -"Filter by infrastructure feature ID"New value: +"Filter by infrastructure feature ID - resolve via list_infrastructure_assets"
    • changedInput schema / properties / vendor_id / description
      Previous value: -"Filter by vendor ID"New value: +"Filter by vendor ID - resolve via list_vendors"
    • changedInput schema / properties / work_order_id / description
      Previous value: -"Filter by work order ID"New value: +"Filter by work order ID - resolve via list_work_orders"
  2. Changed2 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "Repair",
      -  "PM",
      -  "Operation",
      -  "Replacement",
      -  "Decommission"
      -]New value: +[
      +  "Acquisition",
      +  "Repair",
      +  "PM",
      +  "Operation",
      +  "Replacement",
      +  "Decommission",
      +  "Other"
      +]
    • addedInput schema / properties / vendor_id
      Added value: +{
      +  "description": "Filter by vendor ID",
      +  "format": "uuid",
      +  "pattern": "^([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})$",
      +  "type": "string"
      +}
  3. Changed5 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 / feature_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 / page / maximum
      Added value: +9007199254740991
    • 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. Changed5 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 / feature_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 / page / maximum
      Removed value: -9007199254740991
    • 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. Changed5 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 / feature_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 / page / maximum
      Added value: +9007199254740991
    • 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

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: returned amounts are bare numbers with no currency, so a separate settings call is required before quoting a monetary figure. That is exactly the kind of context annotations cannot carry, though it says nothing about ordering, totals, or what a row contains.

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 doing distinct work: purpose, filters, and the currency caveat. The most consequential warning is placed last but is the most memorable line, and there is no filler.

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?

With no output schema, the description carries the burden of explaining returned values, and it covers the highest-risk ambiguity (currencyless amounts) plus the dependency on get_organization_settings. It stops short of describing the cost-row shape or whether all pages are merged, though the schema notes automatic pagination.

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 UUID formats, the category enum, and pagination defaults all documented inline, so the baseline is 3. The description's filter list mirrors the schema rather than adding semantics like whether filters AND together or which parameter to prefer for date scoping.

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?

The description states a specific verb (list) and resource (cost rows for infrastructure features), and its scoping to infrastructure features distinguishes it from the generic list_asset_costs sibling. It never names that sibling explicitly, so the differentiation is implicit rather than spelled out.

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?

It enumerates the available filter dimensions (feature, work order, vendor, category, date range), which implies how the tool is used, and it gives one concrete cross-tool instruction: call get_organization_settings for currency_code. There is no guidance on when to prefer this over list_asset_costs or get_infrastructure_asset_cost, and no statement about filters being combinable.

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