Skip to main content
Glama

List asset condition assessments

list_asset_condition_assessments
Read-onlyIdempotent

List point-in-time condition assessments recorded against assets. Filter by asset, assessor, method, condition score range, or assessment date range. Condition scores are 0-100: 85+ Excellent, 70-84 Good, 55-69 Fair, 40-54 Poor, below 40 Critical. 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_asset_condition_assessments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: all pages fetched automatically)
methodNoFilter by method (visual | detailed | vendor)
asset_idNoFilter by asset ID - resolve via list_assets
per_pageNoItems per page (default: 1000, max: 1000). All pages are fetched automatically.
assessor_idNoFilter by assessor user ID - resolve via list_users
condition_maxNoMaximum condition score (0-100)
condition_minNoMinimum condition score (0-100)
assessed_on_toNoFilter assessments on/before this date (YYYY-MM-DD)
assessed_on_fromNoFilter assessments on/after this date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / assessor_id / description
      Previous value: -"Filter by assessor user ID"New value: +"Filter by assessor user ID - resolve via list_users"
    • changedInput schema / properties / asset_id / description
      Previous value: -"Filter by asset ID"New value: +"Filter by asset ID - 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 / page / maximum
      Added value: +9007199254740991
  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 / page / maximum
      Removed value: -9007199254740991
  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 / page / maximum
      Added value: +9007199254740991
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: the 0-100 score bands (85+ Excellent down to below 40 Critical) and the warning that amounts are bare currency-less numbers. It does not cover pagination or result volume, but the schema's page/per_page text handles that.

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 sentences, each carrying distinct payload — what it lists, what can be filtered, and two non-obvious data conventions. Scope is front-loaded before filtering and caveats, with 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?

Nine optional parameters with rich annotations and no output schema; the description covers filtering, score interpretation, and the currency caveat, and the schema covers pagination. What remains unstated is the returned record shape and ordering, a minor gap for a read-only list.

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 baseline is 3; the description earns above that by explaining what a condition score means (0-100 with named bands) and confirming that the date filters are range bounds on assessment date, which goes beyond the raw min/max/date field labels. It adds nothing for method or assessor_id, which the schema already explains.

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 ('List point-in-time condition assessments recorded against assets') with the 'point-in-time' qualifier that separates this historical list from the singular get_asset_condition_assessment and the create/update siblings. It never names an alternative tool explicitly, so differentiation is inferred from the name plus scope 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 Guidelines4/5

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

Enumerates the five filter axes an agent can use, which conveys when this listing is the right call, and adds a concrete cross-tool prerequisite: 'call get_organization_settings for currency_code before stating one.' It stops short of explicit when-not-to-use guidance or naming sibling tools to prefer for a single record.

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