Skip to main content
Glama

Excerpt lines by number

bpj_surrounding_lines
Read-onlyIdempotent

Extract surrounding lines with their source line numbers for review.

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": {
      "text": "<text>",
      "line": "<line>",
      "radius": "<radius>"
    },
    "name": "bpj_surrounding_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYes
textYes
radiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral detail beyond them: results carry their source line numbers. It does not disclose what happens when the target line exceeds the text length, how lines are counted, or whether the radius is clamped at the document edges.

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 eleven-word sentence with zero padding and the core action front-loaded. It is efficient, though its brevity is closer to under-specification than to tight writing.

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?

A simple three-parameter read tool whose annotations fully cover safety, and the description correctly signals that output includes line numbers. Against that low bar it is nearly adequate, but with no output schema and 0% parameter documentation, edge-case behavior for the required radius and line values is left entirely to inference.

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% – the parameters carry only bare titles ("Target line", "Source text", "Lines either side"), so the description must compensate and largely does not. "Surrounding lines" loosely maps to radius and "source line numbers" to line, but there is no explanation of radius=0 behavior, what happens if line is past the end of text, or the relationship between the 1..6001 line bound and the 6000-character text cap.

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 pairs a specific verb ("Extract") with a specific resource ("surrounding lines") and notes that source line numbers are included, which tells an agent what it gets back. It stops short of naming how it differs from line-oriented siblings such as bpj_keyword_in_context_lines, so it is clear but not fully differentiated.

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 tool, when not to, or which sibling to pick instead (e.g. keyword-in-context vs. by-line-number extraction). The phrase "for review" is the only hint at a use case and it is vague.

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.