Skip to main content
Glama

List infrastructure asset inspections

list_infrastructure_asset_inspections
Read-onlyIdempotent

List inspections recorded against infrastructure assets. Filter by feature, inspector, method, condition score range, or inspection date range.

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_inspections"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: all pages fetched automatically)
methodNoFilter by inspection method (e.g. CCTV, visual)
per_pageNoItems per page (default: 1000, max: 1000). All pages are fetched automatically.
feature_idNoFilter by infrastructure asset (feature) ID - resolve via list_infrastructure_assets
inspector_idNoFilter by inspector user ID - resolve via list_users
condition_maxNoMaximum condition score (0-100)
condition_minNoMinimum condition score (0-100)
inspection_date_toNoFilter inspections on/before this date (YYYY-MM-DD)
inspection_date_fromNoFilter inspections on/after this date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / feature_id / description
      Previous value: -"Filter by infrastructure asset (feature) ID"New value: +"Filter by infrastructure asset (feature) ID - resolve via list_infrastructure_assets"
    • changedInput schema / properties / inspector_id / description
      Previous value: -"Filter by inspector user ID"New value: +"Filter by inspector user ID - resolve via list_users"
  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 / 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
  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 / 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
  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 / 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
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive/closed-world behavior, so the safety profile is covered. The description adds no behavioral context beyond that — no note on result volume, default full-fetch behavior, or ordering — so it earns only the baseline credit consistent with annotations.

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, front-loaded with the resource scope followed by the filtering capability. No filler, no repetition of the title.

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, zero-required read tool with full schema coverage and clear annotations, the description plus schema is sufficient to invoke correctly. A brief note on result ordering or the automatic pagination behavior would close the remaining gap, but nothing essential is missing.

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%, and the schema already documents each filter including UUID resolution hints and date format. The description merely restates the filter categories (feature, inspector, method, condition range, date range) without adding meaning such as how condition_min/max combine or how date bounds interact.

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 (List) and a specific resource (inspections recorded against infrastructure assets), which is clearly narrower than list_infrastructure_assets. It does not explicitly contrast with get_infrastructure_asset_inspection or list_infrastructure_asset_* siblings, but the resource scope is unambiguous.

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?

The second sentence enumerates filter dimensions, which implies 'use this to query/filter inspection records,' but never states when to choose this over list_infrastructure_assets or get_infrastructure_asset_inspection for a single record. Usage is inferable rather than guided.

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