Skip to main content
Glama

Straighten typographic quotes

bpj_straighten_smart_quotes
Read-onlyIdempotent

Convert common curved and low typographic quotation marks to ASCII 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_straighten_smart_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds modest behavioral value by scoping the transform to 'common curved and low' quotes, implying other characters pass through untouched, but it does not say what happens on oversized input or whether straight quotes are left alone.

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 the verb and target character class immediately visible; nothing is redundant or buried.

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, pure-string transform with rich annotations and no output schema, the definition is mostly sufficient. It still omits the edge behavior an agent might care about: characters beyond the listed quote types, straight quotes already present, and what happens when input exceeds 6000 characters.

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% and the single parameter carries only a title ('Source text') and maxLength 6000. The description implies the parameter is the text to be transformed but adds no format or limit information. The parameter is self-evident enough that the meaning is not obscured, so a baseline 3 fits.

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 ('Convert') and a specific resource ('curved and low typographic quotation marks to ASCII quotes'), which leaves no ambiguity about the operation. The sibling catalog contains unrelated utility/benchmark tools, so no explicit sibling differentiation is needed, but the description also does not name any boundary tool.

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 implied by the narrowness of the transform: pass text containing curly or low quotes and get ASCII quotes back. There is no explicit statement of when to choose this over a general text-normalization sibling, nor any note on input prerequisites such as the 6000-character limit.

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.