Skip to main content
Glama

Create LoS measurement

create_los_measurement

Record a new LoS measurement value. Requires los_measurements:write scope. Resolve los_measure_id first via list_los_measures.

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": {
      "los_measure_id": "<los_measure_id>",
      "period_type": "<period_type>",
      "period_start": "<period_start>",
      "period_end": "<period_end>",
      "actual_value": "<actual_value>"
    },
    "name": "create_los_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoNotes or context for this measurement
is_autoNoWhether this is an auto-calculated value (default: false)
period_endYesPeriod end date (ISO 8601, required, e.g., "2026-03-31")
period_typeYesPeriod type (required)
actual_valueYesMeasured value (required)
period_startYesPeriod start date (ISO 8601, required, e.g., "2026-01-01")
los_measure_idYesLoS measure ID (required) - resolve via list_los_measures

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / los_measure_id / description
      Previous value: -"LoS measure ID (required)"New value: +"LoS measure ID (required) - resolve via list_los_measures"
  2. Changed3 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 / los_measure_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. Changed3 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 / los_measure_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. Changed3 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 / los_measure_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

A3.8/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, non-idempotent mutation. The description adds important auth and prerequisite context, but it does not disclose duplicate-creation behavior or confirm whether repeated calls create multiple measurements.

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 with no wasted wording. The primary action is front-loaded, followed by the permission requirement and prerequisite in a logical order.

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 create mutation with rich schema coverage and annotations covering safety traits, the description provides enough context to call the tool correctly. The main remaining gap is duplicate-creation behavior, which matters given idempotentHint=false.

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%, so all seven parameters are already documented in the input schema. The description only repeats the los_measure_id resolution instruction, adding little beyond the schema baseline.

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 uses a specific verb and resource: "Record a new LoS measurement value." It clearly distinguishes creating a measurement from listing measures, but does not explicitly differentiate it from siblings such as create_los_measure or update_los_measurement.

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?

It gives useful usage context: the required write scope and the prerequisite to resolve los_measure_id via list_los_measures first. It does not, however, state when to use this versus update_los_measurement or bulk_create.

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