tdmcp

Connect RSS feed bus

connect_rss_feed_bus

Build an RSS/Atom feed scaffold with sanitized item rows, category maps, refresh policy, and adapter source, enabling editorial feed management within TouchDesigner.

Instructions

Create an RSS/Atom/editorial feed scaffold with sanitized item rows, category maps, refresh policy, adapter source, and copyright/sanitization notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_rss_feed_bus"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	rss_feed_bus
`active`	No
`feed_label`	No		editorial_feed
`item_count`	No
`adapter_url`	No		http://127.0.0.1:9082/feed.xml
`parent_path`	No	Parent COMP for the RSS scaffold.	/project1
`adapter_mode`	No		rss_atom
`category_count`	No
`refresh_interval_sec`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already indicate non-read-only, non-destructive, open-world behavior, so the description adds some context by listing the scaffold's contents (sanitized item rows, category maps, refresh policy). However, it does not disclose potential side effects, permissions, or how 'connect' differs from 'create', leaving the behavioral profile only partially complete.

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 a single, dense sentence that front-loads the primary action and lists key features. It is efficient with no filler, though the list could be more readable if broken into shorter structures.

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

Completeness2/5

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

With 9 optional parameters, no output schema, and no usage guidance, the description is insufficient. It does not explain what the resulting scaffold looks like, what 'connect' means in this context, or what return values to expect, leaving the agent without a complete picture.

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 coverage is only 22% (name and parent_path have descriptions). The description mentions concepts like adapter source, refresh policy, and category maps, which loosely map to parameters (adapter_url, refresh_interval_sec, category_count), but it does not explain each parameter's meaning or usage explicitly. Given the low schema coverage, the description fails to fully compensate.

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?

The description clearly states the tool creates an RSS/Atom/editorial feed scaffold with specific components (sanitized item rows, category maps, etc.), making the purpose specific. However, the tool name uses 'connect' while the description says 'Create', creating slight ambiguity about whether it establishes a connection or builds a scaffold.

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. It does not mention any conditions, prerequisites, or references to sibling tools like other connect_* or create_* tools, leaving the agent without decision-making context.

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

Deploy Server