Skip to main content
Glama

Get Fixed Assets

get_fixed_assets
Read-onlyIdempotent

List fixed assets on the register with cost, net book value, monthly depreciation and status. Returns total_cost, total_accumulated_depreciation and total_nbv for the active assets: quote those, never add the register up yourself. Use when the user asks about their asset register, depreciation schedules, NBV, or capital items tracked per asset. Filter by active, disposed, or all.

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": "get_fixed_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by asset status. Defaults to active.
companyNoWhich company to read, by name or id, when the account has more than one (see list_companies). Leave it out to use the only company, or the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no output schema, the description carries the return-value burden and does so: it names the aggregate fields returned (total_cost, total_accumulated_depreciation, total_nbv) and notes they cover active assets. It also adds a real guardrail — 'quote those, never add the register up yourself' — which prevents a common arithmetic error that annotations cannot express.

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?

Four short sentences in a deliberate order: what it lists, what it returns, when to reach for it, and the filter option. Nothing is repeated and no sentence is filler.

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

Completeness5/5

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

For a two-parameter read-only listing tool with full schema coverage and annotations covering safety, the description supplies purpose, triggers, return fields and a usage guardrail. An agent has everything needed to select and call it correctly.

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 both parameters are already documented in structured form. The description's 'Filter by active, disposed, or all' merely restates the enum, and the 'company' parameter is never mentioned, so no meaning is added beyond the schema. Baseline 3 applies.

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 ('List fixed assets on the register') and enumerates exactly what each record carries: cost, net book value, monthly depreciation and status. The phrase 'capital items tracked per asset' also implicitly separates it from aggregate tools like get_balance_sheet or get_capital_allowance_hint.

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 concrete trigger phrases: 'asset register, depreciation schedules, NBV, or capital items tracked per asset'. That is clear when-to-use guidance, but there is no when-not guidance and no named alternative for related questions (e.g. capital allowances), so it falls short of a 5.

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