Skip to main content
Glama

Interpolate interior numeric gaps

bpj_table_linear_gap_fill
Read-onlyIdempotent

Interpolate missing numeric cells between observed rows at equal spacing, leaving exterior gaps untouched.

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": {
      "rows": "<rows>",
      "column": "<column>"
    },
    "name": "bpj_table_linear_gap_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

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 readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real behavioral value with the interpolation method ('at equal spacing') and the edge policy ('exterior gaps untouched'), but says nothing about how non-numeric or single-value columns are handled or what the call returns.

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 sentence, front-loaded with the action and immediately qualified by the scope constraint. Nothing is wasted and no clause is redundant.

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?

No output schema exists, so the description must imply the result form, which it only weakly does. For a transformation tool taking a raw JSON record array, it should state the input encoding and the handling of non-numeric or ambiguous cells.

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 schema supplies little beyond titles ('Record array (JSON)', 'Column name'). The description clarifies that rows are row-wise records and that the target is a single numeric column, though it never specifies the JSON string encoding or the expected record shape.

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?

Specific verb (interpolate) plus resource (missing numeric cells) and a clear scope boundary: interior gaps between observed rows, exterior gaps untouched. That scope clause implicitly separates it from the forward_fill/backward_fill siblings without naming them.

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 'leaving exterior gaps untouched' clause implies the usage context, but it never states when to pick this over bpj_table_forward_fill or bpj_table_backward_fill, nor what happens when there are no interior gaps. Usage is inferable rather than stated.

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.