Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_noise_texture

Apply a subtle noise/grain texture to any frame to reduce banding and add a film-like finish. Adjust scale and opacity for control.

Instructions

Add a subtle noise/grain texture overlay to a frame.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "create_noise_texture"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoNoise scale (default: 1)
nodeIdYesTarget frame
opacityNoNoise opacity (default: 0.05)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It conveys an additive overlay operation rather than a destructive replacement, but it does not explain whether repeated calls stack, how the effect integrates with existing effects/fills, or whether the operation is reversible.

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?

The description is a single, efficient sentence that leads with the action and result. There is no filler, repetition, or unnecessary detail.

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 simple three-parameter mutation tool without an output schema, the description plus schema is minimally sufficient. However, it omits behavioral context and usage differentiation, so an agent is not fully equipped to invoke it with confidence among many related design tools.

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?

The input schema already describes all parameters (nodeId as target frame, scale, and opacity with defaults), so schema coverage is 100%. The description adds only the qualitative idea of 'subtle', which does not meaningfully extend the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action ('Add') and the resource ('noise/grain texture overlay') plus the target ('a frame'). It is immediately distinguishable from the large set of sibling create_ and set_effect tools.

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?

No guidance is provided about when to choose this tool over alternatives like set_effects or set_image_fill, and there are no exclusions or conditional use cases. The agent must infer the intended use from the tool name and 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