Skip to main content
Glama

inspect_color_dna

Retrieve the mathematical slider values and Tone Curves for a specified Color DNA profile, with an optional custom catalog path, to review its exact color settings.

Instructions

Inspect the full mathematical sliders and Tone Curves of a specific Color DNA profile.

Args: dna_id: The exact Color DNA ID (e.g., "film_emulation_001"). catalog_path: Optional custom path to color_dna_catalog.json.

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": {
      "dna_id": "<dna_id>"
    },
    "name": "inspect_color_dna"
  }
}

Input Schema

NameRequiredDescriptionDefault
dna_idYes
catalog_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; "Inspect" plus an output schema implies a pure read, but it does not explicitly state that nothing is modified. It does add useful context that the returned data is the *full* slider and Tone Curve set (as opposed to a summary), and that the catalog can be relocated via catalog_path, but says nothing about behavior when dna_id is unknown or the catalog is missing.

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?

Front-loaded one-line summary followed by an Args block, with no filler sentences. Format is idiomatic and scannable, though the Args section largely restates parameter names.

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?

An output schema exists, so return structure need not be explained, and both parameters get at least a line of explanation. What is missing is the relationship to list_color_dna for obtaining valid IDs and any note on failure behavior when the ID or catalog is invalid.

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 coverage is 0%, so the description must compensate, and it does for both parameters: dna_id is documented with a concrete example format ("film_emulation_001") and catalog_path is described as an optional custom path to color_dna_catalog.json. It does not say when overriding the catalog path is appropriate or whether dna_id must come from list_color_dna, so the compensation is partial.

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 ("Inspect") plus resource ("a specific Color DNA profile") and names what is exposed ("full mathematical sliders and Tone Curves"), which separates it from list_color_dna and blend_color_dna. It stops short of explicitly naming those siblings, but the scope difference is inferable.

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 only implied: you call this when you have an exact dna_id and need the complete parameter set rather than a listing or a blend. There is no stated prerequisite such as needing list_color_dna to discover valid IDs, and no when-not-to-use guidance.

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