Skip to main content
Glama

Remaining roll length

bpj_material_roll_remaining
Read-onlyIdempotent

Estimate remaining length of a tightly wound uniform roll from caliper, core diameter, and outer diameter.

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": {
      "outside": "<outside>",
      "core": "<core>",
      "caliper": "<caliper>"
    },
    "name": "bpj_material_roll_remaining"
  }
}

Input Schema

NameRequiredDescriptionDefault
coreYes
caliperYes
outsideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavior needs no restating. The description adds two genuinely useful facts beyond them: the result is an 'estimate' rather than an exact value, and it assumes a tightly wound uniform roll. It does not mention what happens if outside diameter is less than core diameter or how caliper variance affects accuracy.

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 the verb, resource, and inputs in that order and no filler. Every clause earns its place.

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 three-parameter closed-form calculator with full annotation coverage, this is close to sufficient. The main remaining gap is that with no output schema, the return value's unit and format are never stated, leaving the agent to infer millimetres from the input titles.

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 carries real weight here, and it does map each of the three inputs by name (caliper, core diameter, outer diameter). It adds no clarification of 'single-layer caliper', no ordering constraint that outside must exceed core, and no note that output length is in the same millimetre units as the inputs.

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 resource ('remaining length of a tightly wound uniform roll') and enumerates the three inputs used. It is clearly distinguishable from geometry siblings like bpj_material_coil_winding_space or bpj_material_filament_spool, though it never names an alternative.

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?

The phrase 'tightly wound uniform roll' implicitly defines the applicability precondition, which is useful guidance about when the estimate is valid. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to a sibling tool for non-uniform or loosely wound rolls.

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.