Skip to main content
Glama
Meteor-Simulation

BULC MCP

Official
by Meteor-Simulation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Spr update sprinkler head

spr_update_sprinkler_head
Idempotent

Update one sprinkler head's K-factor, activation temperature, RTI, type, nozzle fields, and spray profile or per-head overrides; applied FDS copies are rebuilt.

Instructions

Update one pipe-network sprinkler head: K / activation temperature / RTI / type, its shared spray profile (sprayProfileId), per-head spray overrides (spray = &PROP keys, particle = &PART keys, inherit = keys to hand back to the profile, clearSpray = drop all). Applied FDS copies of the head are rebuilt. For many heads or obstacle/DEVC sprinklers use spr_set_head_spray. [bulc-mcp rules] SPR-010, SPR-011 — bulc_knowledge_search ""

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSprinkler head ID
rtiNoNew Response Time Index (m·s)^½
zoneNoDeluge zone
sprayNoPer-head FDS &PROP overrides — same keys as spr_upsert_spray_profile.prop (e.g. {"particles_per_second":10000,"spray_angle":[0,70]}).
lineNoNoLine number
inheritNoOverride keys to remove so the head follows its profile again (prop/part key names)
kFactorNoNew K-Factor, metric L/(min·bar^½)
disabledNoExclude from the calculation
headTypeNoNew type: pendant | upright | sidewall
particleNoPer-head FDS &PART droplet overrides — same keys as spr_upsert_spray_profile.part (e.g. {"diameter":800,"age":600}).
clearSprayNoRemove every per-head spray override (K / activation temperature / RTI back to the profile)
nozzleKindNoclosed (sprinkler) | open (open nozzle) | drain (drain hole)
clearFieldsNoRemove these nozzle fields (requiredPressure → back to the design default)
nozzleModelNoNozzle model name
activationTempNoNew activation temp (°C)
coverageRadiusNoNew coverage radius (m)
sprayProfileIdNoLink the head to this shared spray profile (takes the profile K / activation temperature / RTI unless given here)
requiredPressureNoRequired discharge pressure of this nozzle [MPa]
orificeDiameterMmNodrain orifice diameter [mm] (K is recalculated unless kFactor is given)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false. The description adds real behavioral context beyond that: 'Applied FDS copies of the head are rebuilt' and the override lifecycle semantics (inherit hands keys back to the profile, clearSpray drops all). It stops short of explaining reload timing or response shape, so not a 5.

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?

Action and edit surface are front-loaded, and the alternative is placed last. The parenthetical parameter inventory makes one dense sentence but each clause carries distinct semantics; the trailing rules reference adds minor noise but is purposeful.

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

Completeness4/5

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

For a 19-parameter mutation tool with full schema coverage and annotations, the description covers the override model, the profile linkage, the rebuild side effect, and the sibling alternative. No output schema exists, yet the description does not describe what the update returns, which is the main remaining gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by defining the override model (spray = &PROP keys, particle = &PART keys, inherit = keys to remove, clearSpray = drop all) and cross-referencing spr_upsert_spray_profile for key vocabularies. That adds meaning the flat schema does not convey.

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 a specific verb and resource ('Update one pipe-network sprinkler head') and enumerates the editable facets (K, activation temperature, RTI, type, spray profile, per-head overrides). It also names the sibling it is not (spr_set_head_spray), so an agent can distinguish it without opening either schema.

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 routes to the alternative: 'For many heads or obstacle/DEVC sprinklers use spr_set_head_spray.' The condition (single head vs. many/obstacle/DEVC) that selects each tool is spelled out, and it references the governing bulc rules for deeper guidance.

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