Skip to main content
Glama
the-real-talk

the-real-talk

create_effect_style

Creates a local effect style from a named set of up to eight effects, such as shadows or blurs, and rejects duplicate names to prevent overwrites.

Instructions

Create a local effect style from effects (same shape as set_effects). Refuses an existing name.

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": {
      "name": "<name>",
      "effects": "<effects>"
    },
    "name": "create_effect_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
effectsYes

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 at all, the description carries the full disclosure burden, and it does cover two useful traits: the style is "local" (not a published/library style) and it fails on duplicate names rather than overwriting. It says nothing about required permissions, whether the new style is auto-applied to any selection, or what is returned (an id? a node?) so the agent cannot chain a follow-up call confidently.

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 short sentences, zero filler, with the create action and the scope (local) front-loaded before the failure constraint. Nothing could be cut without losing content.

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 mutation tool with no annotations, no output schema, and a nested effect payload containing bound-variable fields, the definition leaves meaningful gaps: return value, permission requirements, and the semantics of radiusVariable/colorVariable style bindings are all unaddressed. What it does cover (local scope, duplicate-name refusal, payload shape via set_effects) is accurate but thin relative to the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is the only source of meaning, and it supplies very little: "same shape as set_effects" is a cross-reference an agent may not be able to resolve, and "effects" is a nested array of up to 8 objects with four type enum values plus several untyped *Variable binding fields that go entirely unexplained. The only parameter-level insight is that "name" must be unique, which is grounded but insufficient for a two-parameter tool with a rich nested payload.

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 ("Create a local effect style from effects"), and the word "effect" distinguishes it from create_paint_style and create_text_style without needing to enumerate them. The parenthetical pointing at set_effects for the payload shape further sharpens what this tool consumes, though it doesn't explicitly rule out the sibling style-creation tools.

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?

"Refuses an existing name" gives one concrete precondition an agent must respect, which is real guidance. However, there is no statement of when to reach for this versus set_effects (apply directly) or apply_style (reuse an existing style), so the agent must infer the create-vs-apply decision on its own.

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