Skip to main content
Glama

style_set_blend_mode

Set a layer's blend mode to control how it visually interacts with layers below, using modes such as multiply, screen, or overlay.

Instructions

Set a layer's blend mode against layers below it.

mode is one of: normal, multiply, screen, overlay, darken, lighten, difference, addition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
layer_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions setting a blend mode and lists allowed values, but does not disclose side effects, whether it overrides existing settings, error handling, or any permissions needed.

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 concise sentences with no redundant information. The first states the purpose, the second lists the allowed enum values. No fluff.

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?

The tool is simple, and the description covers the basic action. However, lacking usage guidelines and complete parameter semantics reduces completeness. An output schema exists but isn't referenced.

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 has 0% description coverage. Description adds value for 'mode' by listing allowed values but leaves 'layer_id' unexplained. This partial compensation results in a borderline adequate score.

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?

Description clearly states the verb 'Set' and the resource 'layer's blend mode against layers below it'. It distinguishes from sibling tools like layer_set_opacity and style_set_single_symbol by being specific to blend modes.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., other style tools) or any prerequisites. It only states the function without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/piatkowski/qgis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server