Skip to main content
Glama

get_cop_layer

Read image layer data from a COP node, inspect cable output wires, and optionally check per-pixel wire-sum statistics such as blend-weight totals.

Instructions

Get image layer data from a COP node.

A cable output (more than one wire) answers is_cable and wires (name, data type and each wire's layer summary); copernicus_layer is the wire named by wire (index or name, default the first), see layer_read. wire_sum=True adds min/max/average of the per-pixel sum of the one-channel wires, e.g. to check that blend weights sum to 1.

Args: node_path: Path to the COP node. output_index: Output connector index. wire: On a cable output, the wire to read (index or name). wire_sum: On a cable output, stats of the per-pixel sum of its wires.

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": {
      "node_path": "<node_path>"
    },
    "name": "get_cop_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
wireNo
wire_sumNo
node_pathYes
output_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.29.0
    • addedInput schema / properties / wire
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Wire"
      +}
    • addedInput schema / properties / wire_sum
      Added value: +{
      +  "default": false,
      +  "title": "Wire Sum",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  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?

With no annotations, the description carries the full burden and does meaningful work: it discloses that a cable output changes the returned shape (is_cable, wires with name/type/per-wire summary), that copernicus_layer defaults to the first wire, and that wire_sum adds min/max/average of the per-pixel sum. It does not say whether the node is cooked, how invalid node_path or out-of-range wire is reported, or anything about permissions/performance. Solid disclosure of conditional behavior, incomplete on failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single-line purpose is front-loaded, and detail follows in a logical order: cable-output shape, wire selection, then the optional stat. There is mild redundancy — the cable/wire behavior is restated in the Args block after the prose paragraph — but no sentence is 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?

With 4 parameters, no annotations, and no output schema, the description supplies enough for correct invocation: what the return differs by, how to pick a wire, and what the optional flag adds. Missing pieces are operational (cook state, error behavior, node_path format), which limit confidence but do not block a caller.

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 description coverage is 0%, so the description must compensate, and its Args block does cover all four parameters. It adds meaning the schema cannot: wire accepts "index or name" with the first wire as default (important given the int|string anyOf), wire_sum computes per-pixel sum stats, and output_index is a connector index. node_path (path syntax) and output_index (range/default) remain thinly described beyond their field names.

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?

"Get image layer data from a COP node" is a specific verb+resource, and the follow-up sentence clarifies that the payload differs for cable vs single-wire outputs. An agent can distinguish this from get_cop_geometry, get_cop_vdb, and get_cop_info by resource (layer data, not geometry/voxels/node info). It stops short of naming those siblings explicitly, so it is clear but not differentiating by comparison.

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?

Usage is implied rather than stated: the description motivates wire_sum with a concrete case ("to check that blend weights sum to 1") and defers wire semantics to layer_read. There is no explicit when-to-use/when-not-to-use guidance or stated alternative for retrieving layer data from a non-COP source, so an agent must infer selection from the resource description alone.

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