Skip to main content
Glama
Meteor-Simulation

BULC MCP

Official
by Meteor-Simulation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Spr upsert spray profile

spr_upsert_spray_profile

Create, update, or delete shared FDS spray profiles for sprinkler and water-mist heads, with presets, validation, and head assignment.

Instructions

Create, update or delete a shared SPRAY PROFILE — the FDS 6.10.1 &PROP+&PART template (flow, spray pattern, droplet size distribution, breakup, drag, evaporation, surface film, parcels) that sprinkler and water-mist heads reference. Omit id (or give a new id) to create: it starts from preset (default std_pendant_k80) or copy_from. With an existing id, preset overwrites its values, prop/part merge keys and unset_prop/unset_part return keys to the FDS default. Presets: standard, quick response, ESFR, residential, water mist low (12 bar) / intermediate (21 bar) / high (70-100 bar) — spr_list_summary {include_presets:true}. assign_to links heads to the profile (pipe heads take its K, activation temperature and RTI). Every edit is checked like FDS (K or pressure alone = ERROR 238, no DIAMETER = 214, equal SPRAY_ANGLE = 231, bad EVAP_MODEL = 224) for the profile and every head using it; on error nothing changes. Per-head overrides: spr_set_head_spray.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoProfile id. Existing = update; new or omitted = create
nameNoDisplay name
partNoFDS 6.10.1 &PART water-droplet keys (lowercase FDS names; diameters in µm). Unset = FDS default.
propNoFDS 6.10.1 &PROP spray keys (lowercase FDS names, FDS units). Unset = FDS default.
deleteNoDelete the profile (refused while heads use it or if it is the last one)
presetNoPreset to start from (new) or to overwrite the values with (existing)
assign_toNoLink heads to this profile
copy_fromNoNew profile = copy of this profile id
unset_partNopart keys to remove (FDS default)
unset_propNoprop keys to remove (FDS default)
fds_part_idNoFixed &PART ID written for this profile (for PART_ID in AMPUA/MPUV devices; "" = derive)
fds_prop_idNoFixed &PROP ID written for this profile ("" = derive)
make_defaultNoMake it the project default profile (new heads and heads without a profile follow it)
advanced_partNoExtra raw &PART 'KEY=VALUE' entries; [] clears
advanced_propNoExtra raw &PROP 'KEY=VALUE' entries (checked against the FDS 6.10.1 key list); [] clears

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give the generic safety hints; the description goes much further, disclosing that every edit is FDS-validated (specific ERROR codes 238/214/231/224) with atomic 'on error nothing changes' semantics, and that delete is refused while heads use the profile or if it is the last one. This is exactly the extra behavioral context the annotations cannot carry.

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?

It leads with the core purpose and every sentence carries substantive information (routing, validation, presets) with no filler, which is appropriate for a 15-parameter nested tool. The single dense paragraph is harder to scan than a segmented version, costing it the top mark.

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?

For a complex upsert with nested objects and no output schema, the description covers all the modes (create/update/delete), the preset system, validation and atomicity, and head assignment. Nothing critical to invoking it correctly is left out.

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 adds real semantics the schema lacks: the default preset (std_pendant_k80), that preset overwrites an existing profile, that unset_prop/unset_part drop keys back to FDS defaults, and that assign_to makes pipe heads inherit K/temperature/RTI. That elevates it above baseline.

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 precise compound verb (create/update/delete) on a specific resource (shared SPRAY PROFILE = FDS 6.10.1 &PROP+&PART template) and scopes it to sprinkler and water-mist heads. It names the fields it governs and clearly separates itself from spr_set_head_spray (per-head overrides) and spr_list_summary (preset listing).

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

Usage Guidelines4/5

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

Explicitly states the create/update conditions ('Omit id (or give a new id) to create', 'With an existing id, preset overwrites') and routes related tasks to siblings (spr_set_head_spray for per-head, spr_list_summary for presets). It lacks an explicit 'do not use when…' exclusion, but the branching logic is clear enough for correct selection.

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