Skip to main content
Glama

Create infrastructure asset inspection

create_infrastructure_asset_inspection

Record an inspection against an infrastructure feature. Requires infrastructure_asset_inspections: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": {
      "feature_id": "<feature_id>",
      "inspection_date": "<inspection_date>"
    },
    "name": "create_infrastructure_asset_inspection"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFree-form notes
methodNoInspection method (e.g. CCTV, visual)
defectsNoDefect observations (JSON)
feature_idYesInfrastructure asset (feature) ID (required) - resolve via list_infrastructure_assets
attachmentsNoAttachment URLs/paths
inspector_idNoInspector user ID - resolve via list_users
condition_scoreNoCondition score (0-100)
inspection_dateYesInspection date (YYYY-MM-DD, required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / feature_id / description
      Previous value: -"Infrastructure asset (feature) ID (required)"New value: +"Infrastructure asset (feature) ID (required) - resolve via list_infrastructure_assets"
    • changedInput schema / properties / inspector_id / description
      Previous value: -"Inspector user ID"New value: +"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 / defects / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • 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})$"
  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 / defects / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • 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})$"
  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 / defects / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • 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})$"
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the write, non-idempotent, non-destructive safety profile, so the bar is lower. The description adds genuine context beyond them by naming the required 'infrastructure_asset_inspections:write' scope, which is not derivable from structured fields. It stops short of explaining what non-idempotency means in practice (duplicate records on retry) or whether missing optional fields such as defects are stored as empty.

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 sentences, zero waste, and the operation is front-loaded ahead of the access requirement. Nothing could be trimmed without losing information.

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

Completeness3/5

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

For a mutation with 8 parameters, a nested free-form JSON field, and no output schema, the description is thin. Annotations cover the safety profile and the schema covers the fields, so the core is adequate, but the agent gets no guidance on how defect payloads should be shaped or what happens on retry of a non-idempotent create.

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 itself carries the useful resolution hints ('resolve via list_infrastructure_assets', 'resolve via list_users'). The description adds nothing about parameters, so the baseline of 3 applies; the opaque 'defects' free-form JSON object is the one place a sentence would have helped, and it is absent.

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: 'Record an inspection against an infrastructure feature.' This is unambiguous about what is created. It does not, however, differentiate itself from closely related siblings such as create_asset_condition_assessment or update_infrastructure_asset_inspection, so the agent must infer the boundary.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no conditions that select this tool over the update or condition-assessment variants, and no note that an existing inspection should be modified rather than duplicated. The only prerequisite mentioned is the write scope, which is access control rather than usage routing.

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