Skip to main content
Glama

Strict turning points

bpj_series_turning_points
Read-onlyIdempotent

Identify interior rows strictly above or strictly below both neighbours.

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": {
      "values": "<values>"
    },
    "name": "bpj_series_turning_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral nuance beyond that: only interior rows qualify (first and last elements are excluded) and the comparison must be strict, so ties and plateaus are not counted. It says nothing, however, about what is returned (indices, booleans, or values) or how short series are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the key constraint ('strictly', 'interior', 'both neighbours') front-loaded and no filler. It could be marginally improved by naming the concept, but nothing is wasted.

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, side-effect-free one-parameter function whose annotations fully cover safety, the definition is close to sufficient. The main missing piece is the shape of the result — an agent cannot tell whether it receives indices, booleans, or values, and there is no output schema to fall back on.

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%, but there is only one parameter and its title 'Number array (JSON)' plus type string and maxLength 12000 makes the format largely self-evident. The description adds nothing about the parameter — not the JSON encoding of the array, nor the minimum length of 3 needed for any interior row to exist.

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 concrete verb ("Identify") and defines the exact predicate: interior rows strictly above or strictly below both neighbours, i.e. local extrema with ties excluded. It is specific enough to distinguish this from neighbours like bpj_series_constant_runs or bpj_series_lag_differences, though it never uses the term 'turning point' or 'local extremum' to tie back to the tool name.

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?

There is no statement of when to use this versus alternatives (e.g. moving_median for smoothing, constant_runs for plateaus), no prerequisites, and no mention of when it is inappropriate. The only implicit guidance is the word 'interior', which tells the agent endpoints are never returned.

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.