Skip to main content
Glama

capture_device_parameter_snapshot

Read-onlyIdempotent

Capture exposed device parameters for a track/device as persistable JSON, with a live identity check and no hidden plugin state, samples, automation, or mappings.

Instructions

Capture exposed device parameters as persistable JSON, with a consistent live identity check. Not a native preset: excludes hidden plugin state, samples, automation and mappings.

Input Schema

NameRequiredDescriptionDefault
trackIdYestrack-N from list_tracks, return-N from get_set_mixer, or master.
deviceIdYesID from list_devices.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "properties": {
      +      "deviceId": {
      +        "type": "string"
      +      },
      +      "limitation": {
      +        "type": "string"
      +      },
      +      "snapshot": {
      +        "type": "object"
      +      },
      +      "stateVersion": {
      +        "minimum": 1,
      +        "type": "integer"
      +      },
      +      "trackId": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "stateVersion",
      +      "trackId",
      +      "deviceId",
      +      "snapshot",
      +      "limitation"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "error": {
      +        "properties": {
      +          "message": {
      +            "type": "string"
      +          },
      +          "outcome": {
      +            "enum": [
      +              "unknown",
      +              "not_executed"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "message",
      +          "outcome"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "error"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Changed3 schema fields changedv0.3.0
    • changedInput schema / properties / deviceId / description
      Previous value: -"Stable device ID returned by list_devices."New value: +"ID from list_devices."
    • changedInput schema / properties / trackId / description
      Previous value: -"Stable device-owner ID: track-N from list_tracks, return-N from get_set_mixer, or master."New value: +"track-N from list_tracks, return-N from get_set_mixer, or master."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), lowering the bar. The description still adds real behavioral content: the captured payload is persistable JSON, a 'consistent live identity check' is performed, and hidden plugin state, samples, automation and mappings are excluded from scope. The phrase 'live identity check' remains somewhat cryptic, keeping this from a 5.

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 tightly written sentences with zero filler. The core action and the persistable-JSON output are front-loaded, and the exclusion clause that follows is genuinely informative rather than padding.

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?

With an output schema present the return shape need not be described, and annotations cover the safety profile, so the remaining burden is scope and orientation. The description covers excluded content well. The residual gap is that it never says the snapshot is later consumed by recall_device_parameter_snapshot, nor distinguishes itself from the chain/track/group snapshot variants.

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 both parameters are documented in place (trackId referencing list_tracks/get_set_mixer/master, deviceId referencing list_devices). The description adds no additional parameter meaning or syntax, so the baseline of 3 applies.

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 ('Capture exposed device parameters as persistable JSON') and clarifies what it is not ('Not a native preset'). It does not, however, differentiate itself from sibling snapshot tools such as capture_device_chain_snapshot or capture_track_state_snapshot, which the agent must distinguish on its own.

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?

'Not a native preset: excludes hidden plugin state, samples, automation and mappings' bounds the scope and implicitly suggests when to prefer it over save_native_device_preset. But there is no explicit when-to-use statement, no precondition (e.g. that a device must be selected/loaded), and no routing to the related recall_device_parameter_snapshot sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools