Skip to main content
Glama

Trapezoidal integral on uneven samples

bpj_pairs_trapezoid_integral
Read-onlyIdempotent

Integrate consecutive readings using trapezoids on strictly increasing x coordinates.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "bpj_pairs_trapezoid_integral"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds the trapezoidal integration method and the strictly increasing x-coordinate requirement, but does not explain error behavior when x is not strictly increasing or what the result looks like.

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 description is a single front-loaded sentence with no filler. Every phrase contributes to specifying the operation, the method, and the key input constraint.

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?

The annotations cover the safety profile and no output schema exists, so the description need not explain return values. Still, with 0% schema description coverage, the definition leaves important calling details implicit, especially the JSON-string encoding of x and y and the required equal-length pairing.

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 parameter meaning. It identifies x as coordinates and y as readings and adds the 'strictly increasing' constraint for x, but it omits that both parameters are JSON-encoded numeric series strings, that they must be paired and equal-length, and how numeric values are parsed.

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 ('Integrate'), a specific resource ('consecutive readings'), and a specific method ('using trapezoids'). It also states the key scope condition ('strictly increasing x coordinates'), though it does not explicitly differentiate itself from sibling statistical tools.

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 description gives an important precondition ('strictly increasing x coordinates') that implies when the tool is applicable. However, it offers no explicit when-to-use guidance, no when-not guidance, and no named alternatives among the many sibling tools.

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.