Skip to main content
Glama

style-lint

Style lint. Any text in, URL-encoded as the text query parameter (up to 12,000 bytes), a style scorecard out: nine rules (actually filler, sentence-initial Most, ten LLM tell phrases, not-X-but-Y contrast, em dashes, curly quotes, exclamations, repeated words, double spaces), every hit counted with line numbers, a tell/typography/rhythm summary, the rule table beside the verdict. Price: $0.005 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "style-lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to lint (up to 12,000 bytes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses the 12,000-byte input ceiling, the URL-encoding requirement for the query parameter, the structure of the returned scorecard (per-rule hit counts with line numbers, plus tell/typography/rhythm summary), and the paid-call failure mode (HTTP 402 with machine-readable terms) including price and payment rail. What keeps it from a 5 is that the x402 payment flow is stated as a fact but not actionable — no hint about how an agent obtains or attaches payment.

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?

Front-loaded with the purpose, then output, then pricing — the ordering an agent needs. It is a single dense run-on with comma splices and dropped articles, so readability suffers slightly, but nearly every clause carries distinct information (rule list, limits, payment terms) rather than restating the name.

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

Completeness5/5

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

No output schema exists, so the description must describe returns — and it does, specifying hit counts with line numbers, the summary axes, and the accompanying rule table. Combined with the input cap, encoding requirement, and payment failure mode, an agent has everything needed to call this correctly and to anticipate a 402 response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents itself, so the baseline is 3. The description earns an extra point by adding meaning the schema omits: the text must be URL-encoded into the query parameter, and the practical 12,000-byte limit is framed in terms of what gets accepted rather than just restated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Style lint'), then immediately binds input to output: 'Any text in ... a style scorecard out.' The enumerated nine rules (filler, sentence-initial Most, LLM tells, not-X-but-Y, em dashes, curly quotes, exclamations, repeated words, double spaces) pin down scope precisely enough that no sibling tool could be confused with it.

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?

'Any text in' establishes the input domain broadly, so an agent knows it can route arbitrary prose here, and the size cap implicitly signals when to chunk. However, there is no explicit when-to-use vs when-not guidance and no named alternatives among the sibling set (e.g. text-rewriting or grammar tools), leaving routing to inference.

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.

Resources