Skip to main content
Glama

Ramp grade and angle

bpj_geom_ramp_grade
Read-onlyIdempotent

Calculate signed grade, slope length, and incline from horizontal run and elevation change.

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": {
      "run": "<run>",
      "rise": "<rise>"
    },
    "name": "bpj_geom_ramp_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYes
riseYes

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, and destructiveHint=false, so the safety profile is covered. The description adds that the grade is *signed* and that three quantities are returned, which is genuine behavioral context. It omits critical behavioral detail for a calculator with no output schema: whether grade is returned as a ratio or a percentage, whether incline is degrees or radians, and whether units are assumed to be metres.

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?

One front-loaded sentence with no filler; every noun earns its place by specifying either an input or an output. Nothing is buried or restated.

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?

There is no output schema, so the description must explain the return values, and it only names them without units or formats (percent vs. decimal grade, degrees vs. radians). For a simple two-input calculator with annotations covering safety, this is adequate but leaves ambiguity an agent would need to resolve by trial.

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?

With only two parameters and 0% schema description coverage, the description must carry the meaning, and it does map inputs to concepts: 'run' is horizontal run and 'rise' is elevation change. The schema titles add the (m) unit, which the description does not repeat. A modest gap remains because the relationship (rise/run) and the sign convention are only implied.

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 uses a specific verb ('Calculate') and names the concrete outputs (signed grade, slope length, incline) plus the two inputs (horizontal run, elevation change). That makes the tool's function unmistakable. It does not, however, contrast itself with any sibling (e.g. the many bpj_geom_* shape calculators or bpj_units_angle), so it stops short of explicit differentiation.

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 word 'signed' hints that a negative rise (downhill) is meaningful, which is a useful cue, but there is no explicit statement of when to choose this tool over an alternative such as a plain angle converter. No exclusions, prerequisites, or decision rules are given.

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.