Skip to main content
Glama

Direct quotation extraction

bpj_extract_direct_quotations
Read-onlyIdempotent

Extract single-line passages enclosed in matched curly or straight double quotes.

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_direct_quotations"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add extraction semantics. "Matched" and "single-line" are genuine behavioral constraints not present in the schema, but the description says nothing about unmatched or nested quotes or about whether the quote characters themselves are retained in the result, and there is no output schema to fill that gap.

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?

A single front-loaded sentence with no filler and no redundant restatement of the tool name. Every phrase (single-line, matched, curly or straight) constrains behavior and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the return shape is entirely undocumented: an agent cannot tell whether it receives a list of strings, whether quote marks are stripped, how ordering works, or what an empty result looks like. Given the tool's simplicity these are modest gaps, but the description is the only place they could be covered and covers none of them.

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%, so the description should ideally clarify the single `text` parameter. It does so only implicitly: the source of the mined quotations is obviously the input text, and the schema supplies the title "Source text" plus a 6000-character cap. For one self-evident parameter this is adequate but not additive.

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 specific verb ("Extract") and a precisely bounded resource ("single-line passages enclosed in matched curly or straight double quotes"). An agent knows exactly what pattern is being harvested, though nothing distinguishes it from sibling extractors such as bpj_extract_parenthetical_asides.

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?

Usage is only implied through the scope constraints ("single-line", "matched" quotes), which implicitly tell the agent the tool is not for multi-line block quotes or unbalanced quotation marks. There is no explicit when-to-use guidance and no named alternative for cases that fall outside that scope.

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.