Skip to main content
Glama

Drip bed watering time

bpj_material_drip_bed
Read-onlyIdempotent

Estimate the ideal runtime to apply a target depth from the combined flow of identical emitters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "area": "<area>",
      "depth": "<depth>",
      "emitter": "<emitter>",
      "emitters": "<emitters>"
    },
    "name": "bpj_material_drip_bed"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
depthYes
emitterYes
emittersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds a meaningful modeling assumption ('identical emitters', combined flow), but says nothing about output units (minutes vs hours), whether it assumes uniform emission or efficiency losses, or that the result is only an estimate that may need field adjustment.

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?

A single front-loaded sentence with no filler; every clause (estimate, runtime, target depth, combined flow, identical emitters) carries information.

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

Completeness3/5

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

For a simple four-number calculator with full annotation coverage and no output schema, the definition is close to adequate. The missing piece is what the returned runtime is measured in and what assumptions (uniform emitters, no losses) the estimate rests on, which matters for a physical calculation.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry the parametric meaning. It does communicate that the emitters are identical (justifying a single flow value plus a count) and that depth is a target, but it never explains the role of 'area' in the computation, leaving one of four parameters semantically thin.

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 gives a specific verb ('Estimate') and a precise resource ('ideal runtime to apply a target depth from the combined flow of identical emitters'), so an agent can tell this is a drip-irrigation runtime calculator. It does not explicitly distinguish itself from the many sibling material/time calculators, but the domain is narrow enough that no confusion is likely.

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?

Usage is only implied: the agent can infer this applies when sizing a drip-bed watering session, but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent whether to prefer this over a generic flow/time tool such as bpj_little_law_flow_time.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.