Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pp_preset

Apply a named post-processing preset to create or update a PP volume, selecting from presets like horror, cyberpunk, noir, with adjustable intensity and optional actor label.

Instructions

Apply a named post-processing preset. Creates or updates a PP volume. Presets: horror, cyberpunk, noir, dream, underwater, surveillance, vhs_glitch, damage, drunk, frozen, nuclear, sepia, cinematic, neon, thermal.

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": {
      "preset": "<preset>"
    },
    "name": "pp_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoActor label (default: PP_<preset>)
presetYesPreset name
intensityNoScale all values 0-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.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 burden of disclosing side effects. It states 'Creates or updates a PP volume,' which is a key behavioral trait, but omits details such as whether existing settings are overwritten, how intensity scales values, or any required permissions.

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 description is concise and front-loaded with the verb 'Apply.' The preset list is useful but duplicates the schema enum, adding minor redundancy. Overall, it is efficient and well-structured.

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 description covers the core function and side effect but lacks usage guidance and detailed behavioral side effects. With no output schema, it also doesn't describe return values, though the tool is likely straightforward. Adequate for a simple tool but with clear gaps.

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 description coverage is 100%, providing full parameter documentation. The description adds little beyond the schema, except listing presets (which are already in the enum). It does not clarify name or intensity behavior beyond their defaults.

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 states the action ('Apply a named post-processing preset') and the effect ('Creates or updates a PP volume'), distinguishing it from lower-level volume spawn/modify tools. It also enumerates all available presets, making the scope explicit.

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 implies use for applying presets but gives no explicit guidance on when to choose this tool over alternatives like pp_volume_spawn or pp_volume_modify. No exclusions or alternative recommendations are provided, leaving the agent to infer context.

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