Skip to main content
Glama

Prose Coach

Server Details

Deterministic writing filter. Marks 43 AI patterns with the line and the fix.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.1/5 across 1 of 1 tools scored.

Server CoherenceA
Disambiguation5/5

With only a single tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined and distinct from any hypothetical other tools.

Naming Consistency5/5

The tool name follows a clear verb_noun pattern (scan_draft), which is consistent and predictable. Even with one tool, the naming is unambiguous and follows standard conventions.

Tool Count3/5

The server has exactly one tool, which feels thin for a 'Prose Coach' brand. However, the tool is comprehensive for its specific function of scanning for AI patterns, so the count is borderline rather than severely inadequate.

Completeness4/5

The tool covers the core workflow of detecting AI patterns and providing fixes in a single pass. Minor gaps exist, such as no tool for tracking multiple scans or performing batch analysis, but for the stated purpose, the surface is largely complete.

Available Tools

1 tool
scan_draftScan a draft for AI writing patternsA
Read-onlyIdempotent
Inspect

Scan a draft for the patterns that make writing read as AI-generated: banned vocabulary, structural tells (triplets, negation formulas, summary closers, colon chains, flat rhythm), and pattern density scored against the accumulation threshold. Deterministic — the same text always returns the same findings. Run this before showing the user any outward-facing draft: an email, a post, a cover letter, marketing copy, a blog article. Returns each finding with the evidence quoted from the text and the fix.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe draft to scan. Paste the prose itself, not a summary of it.
Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description adds determinism ('same text always returns the same findings') and output structure (evidence quoted and fix). No contradiction with annotations, and these additions help the agent predict behavior.

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?

The description is moderately detailed but every sentence contributes: purpose, pattern categories, determinism, usage timing, and output format. It's slightly longer than minimal but remains focused and front-loaded.

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

Completeness4/5

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

For a single-parameter, no-output-schema tool, the description provides sufficient context: what it scans, how it behaves (deterministic), what it returns (findings with evidence and fix), and when to use it. Some specifics like the accumulation threshold are mentioned but not explained, which is acceptable given complexity.

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?

The schema covers 100% of the parameter, including a description that clarifies the text should be the prose itself, not a summary. The tool description doesn't add additional parameter semantics beyond that, so the baseline of 3 is appropriate.

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?

The description clearly states the tool scans a draft for AI-generated writing patterns, listing specific categories like banned vocabulary and structural tells. This is a specific verb+resource with no ambiguity, and since there are no sibling tools, differentiation isn't needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit guidance on when to use the tool: 'Run this before showing the user any outward-facing draft' with concrete examples. It doesn't mention when-not or alternatives, but there are no sibling tools and the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources