Skip to main content
Glama
ober37

AC Infinity MCP

set_vpd_automation

Enable VPD automation on a port by setting a target VPD value. Uses built-in temperature and humidity sensors to maintain the desired VPD.

Instructions

Enable VPD automation on a port using the built-in temperature and humidity sensors.

Switches the port to VPD mode (atType=8) and sets the VPD target. Uses read-before-write. Defaults to dry_run=True — set dry_run=False to write to the device.

Args: device_id: Device code from discover_devices (e.g. "C58ZA"). port: 1-based port number. target_vpd: Target VPD in kPa, range 0.1–3.0. Typical ranges by stage: seedling/clones 0.8–1.2, veg 1.0–1.5, early_flower 1.0–1.8, mid_flower 1.2–2.0, late_flower 1.2–1.8. dry_run: If True (default), returns the payload that would be sent without writing.

Returns: JSON with action, device_id, port, target_vpd_kpa, dry_run, controller_type, sent, and payload (when dry_run=True). On failure returns {"error": "..."}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes
portYes
target_vpdYes
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses dry_run default and meaning, read-before-write behavior, and return format including error handling. This provides sufficient behavioral transparency.

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?

Description is concise and well-structured. Brief intro, clearly labeled Args section, and Returns section. Every sentence provides necessary information without redundancy.

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?

Given no annotations but presence of output schema, the description covers behavior, parameters, and return format comprehensively. An agent can correctly invoke the tool based on this description.

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 0%, so description compensates fully. Each parameter is explained: device_id source, port 1-based, target_vpd range and typical stage values, dry_run default and effect. Adds significant value beyond schema titles.

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 it enables VPD automation on a port using built-in sensors. The verb 'enable' and resource 'VPD automation on a port' are specific, and the tool is distinct from siblings like set_humidity_automation or set_temperature_automation.

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?

Description mentions switching to VPD mode and setting target, but does not explicitly state when to use this tool over alternatives. No when-not guidance is provided. However, the context of VPD automation is clear enough for an agent to infer appropriate usage.

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/ober37/ac-infinity-mcp'

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