Skip to main content
Glama

Intersection of two selections

bpj_sheet_intersection
Read-onlyIdempotent

Find the overlapping rectangle and number of shared cells between two selections.

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": {
      "range": "<range>",
      "other": "<other>"
    },
    "name": "bpj_sheet_intersection"
  }
}

Input Schema

NameRequiredDescriptionDefault
otherYes
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety is fully covered. The description adds the shape of the result (rectangle + shared cell count), which is helpful given no output schema, but says nothing about empty intersections, ranges that partially fall outside a sheet, or ordering asymmetry.

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, result-focused, with the most important output (overlapping rectangle) stated first and no filler.

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?

With no output schema, the description usefully sketches the return values (rectangle and shared-cell count). However, for a two-required-parameter geometry tool with zero parameter documentation, it omits edge-case behavior an agent would need to invoke it confidently.

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 needs to explain the two range inputs, yet it only says 'two selections'. It never clarifies that both are rectangular A1 ranges, how multi-area or reversed ranges behave, or whether order matters, so it does not compensate for the thin schema.

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 names a specific verb (find) and a precisely bounded result (overlapping rectangle plus shared-cell count) for two ranges. That distinguishes it from neighbors like bpj_sheet_subtract or bpj_sheet_bounding_box, though it never names them explicitly.

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 guidance on when to pick this tool over related sheet-range tools such as subtract, split, or bounding box; the sentence only restates what the operation computes. The agent must infer applicability from the name alone.

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.