Skip to main content
Glama

Curtain fullness and drops

bpj_material_curtain_fullness
Read-onlyIdempotent

Estimate the number of usable fabric widths and achieved fullness for one curtain track.

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": {
      "track": "<track>",
      "fullness": "<fullness>",
      "fabric": "<fabric>"
    },
    "name": "bpj_material_curtain_fullness"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
fabricYes
fullnessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive calculation. The description adds that it is an estimate scoped to one curtain track and mentions usable widths and achieved fullness, but it does not disclose rounding, assumptions, or output format. Given annotation coverage, a 3 is appropriate.

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?

The definition is a single, front-loaded sentence with no filler. Every phrase contributes to the stated calculation purpose.

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?

For a three-parameter calculation tool with no output schema, the definition is too thin: it does not explain the calculation method or what values are returned. It is enough to suggest the domain, but not enough to invoke the tool confidently without inspecting schema titles or guessing the formula.

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 description coverage is 0%, so the description must carry more of the parameter meaning, but it only loosely connects "track" and "fabric" to the computed widths. It does not explain how fullness is applied, how drops are counted, or how the three inputs combine. The schema titles provide units and ranges, but the description adds little beyond them.

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 states a specific verb, "Estimate," and concrete outputs, "usable fabric widths" and "achieved fullness," scoped to "one curtain track." It is clear what the tool computes, though it does not differentiate itself from any sibling material calculator.

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 gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent can infer this is for curtain-track fabric estimation, but there is no routing help among the many material calculators.

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.