Skip to main content
Glama

humanizer_score

Read-onlyIdempotent

Detect AI-writing tells in text. POST prose and get a 0-1 ai_ness score + band (low/medium/high) + the EXACT patterns that fired (AI vocabulary, significance inflation, promotional language, filler phrases, negative parallelism, rule-of-three, em-dash overuse) with sample spans. Explainable, not an opaque classifier - every point is a named, located pattern. Deterministic, no LLM. The rewrite is a separate step.

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": "humanizer_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe prose to score (up to 100k chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavior beyond that: deterministic, no LLM, explainable named-pattern output rather than an opaque classifier. It does not discuss rate limits or cost, but for a pure read-scorer that is minor.

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 core purpose, then output shape, then differentiation from the rewrite step. The parenthetical pattern list is long but earns its place by telling the agent what kinds of findings to expect. Slightly dense, with no wasted framing sentences.

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?

No output schema exists, so the description must carry the return-value burden, and it does: score, band, fired patterns with sample spans. Combined with the single fully documented parameter and safe annotations, an agent has what it needs to call it correctly; only minor gaps (limits, cost) remain.

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 coverage is 100% and there is only one parameter, so the baseline is 3. The description says 'POST prose' but adds no syntax or format guidance beyond what the schema's 'text' field already documents (including the 100k char cap).

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?

A specific verb ('Detect') plus resource ('AI-writing tells in text'), plus the exact output shape (0-1 ai_ness score, band, fired patterns). It also distinguishes itself from the rewrite sibling with 'The rewrite is a separate step', so an agent can route between scoring and rewriting without opening either schema.

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?

Clear context: POST prose, receive a score plus located patterns, and the note that rewriting is a separate step steers agents away from expecting a fix. It stops short of naming the sibling (humanize_text) or stating explicit exclusions, so it is clear context rather than full when/when-not guidance.

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.