Skip to main content
Glama
dqbuilds

singular-mcp-server

by dqbuilds

Update control-node content

singular_update_content

Update control node values in one or more sub-compositions with a single PATCH request. Set text, numbers, colors, images, booleans, selections, and JSON to batch updates and conserve rate limits.

Instructions

Fill control nodes of one or more sub-compositions in a single PATCH. Each update targets a sub-composition (by name or id) and supplies a payload mapping control-node ids → values.

Value formats by node type: text/textarea→string, number→number, image/audio→URL string, color→{r,g,b,a} (0–255) or hex string, checkbox→boolean, selection→option value, json→object. Node ids come from get_model / find_nodes.

Batching multiple sub-compositions here (rather than many calls) conserves rate limit. This sets content only — it does NOT animate; use animate_state or update_and_animate to take on/off air.

Args: app/appToken; updates: [{ subCompositionName | subCompositionId, payload }]; response_format. Returns { success, updatedCount }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoAlias of a registered app instance (see register_app / list_apps). Preferred over a raw token.
updatesYesOne entry per sub-composition to update.
appTokenNoRaw Singular control-app token for a one-off/unregistered instance. If both 'app' and 'appToken' are given, 'appToken' wins.
response_formatNoOutput format: 'markdown' (human-readable) or 'json' (machine-readable). Default 'markdown'.markdown
Behavior4/5

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

Annotations already indicate non-readonly, open world, not idempotent, not destructive. Description adds context: it sets content only, does not animate, and provides value formats per node type. Does not contradict annotations.

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?

Description is concise and well-structured: purpose, value formats, batching, exclusions. Each sentence adds value, though could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all aspects: purpose, parameters, value formats, batching, exclusions, and return value. No output schema, but return is described as { success, updatedCount }.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant meaning: explains value formats per node type, source of node ids, batching benefit, and preference of 'app' over 'appToken'. This goes beyond schema descriptions.

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?

States it fills control nodes of sub-compositions via PATCH, with specific verb 'Fill' and resource 'control nodes of one or more sub-compositions'. Distinguishes from siblings by explicitly noting it does not animate, compared to animate_state and update_and_animate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use this for content-only updates, and directs to animate_state or update_and_animate for animation/taking on/off air. Also mentions batching multiple sub-compositions to conserve rate limit, providing clear when-to-use and alternatives.

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/dqbuilds/singular-mcp-server'

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