Skip to main content
Glama

Parenthetical aside extraction

bpj_extract_parenthetical_asides
Read-onlyIdempotent

Extract innermost parenthetical passages with source offsets.

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>"
    },
    "name": "bpj_extract_parenthetical_asides"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add behavior beyond that. It does add two useful facts: matching is restricted to innermost occurrences, and results carry source offsets. It omits edge behavior such as unbalanced or unclosed parentheses, length limits, and what an offset is measured against.

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 seven-word sentence with the key qualifier ("innermost") and the output trait ("source offsets") front-loaded; there is no filler. It is terse to the point of under-specification, but nothing written 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 one-parameter read-only tool with annotations and no output schema, the description should at least sketch the return shape (list of strings? objects with start/end?) and the offset unit. "With source offsets" gestures at this but leaves the response format and offset basis undefined, so an agent knows what it gets only in outline.

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?

Only one parameter ("text"), which is self-evident, and the schema supplies a title and a maxLength of 6000. Schema description coverage is 0%, so the description ideally would note that input is capped at 6000 characters or that the whole text is scanned, but it adds essentially nothing beyond the parameter name. The single-parameter shape keeps this from being a serious gap.

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?

States a specific verb ("Extract") and a specific resource ("innermost parenthetical passages"), plus a scope qualifier ("innermost") that distinguishes it from a generic parenthetical or quotation extractor among the sibling tools. It stops short of explicitly disambiguating from near-neighbors like bpj_extract_direct_quotations, but the resource is concrete enough to route on.

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 when-to-use guidance, no exclusions, and no mention of alternatives. The word "innermost" implies a nesting policy but the description never says whether outer/nested matches are discarded or reported, which is exactly the decision an agent would need guidance on.

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.