Skip to main content
Glama

check_score

Score a passage 0-100 for AI-likeness (stylometric heuristic). Free, no account.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe passage to score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses cost/auth requirements, the return scale, and that the method is a 'stylometric heuristic' (signalling it is not a definitive classifier), but says nothing about input length limits, scoring reliability, or error behavior.

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?

Two short clauses with zero waste, and the core purpose is front-loaded before the cost/auth footnote.

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 one-parameter scoring tool with no output schema, the description covers what it returns, how, and what it costs. The remaining gaps (input size limits, output precision) are minor rather than blocking.

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?

With one parameter at 100% schema description coverage, the schema already fully documents 'text'. The description adds only the framing of it as a 'passage', which is marginal value; baseline 3 applies.

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 (score), the resource (a passage), the output scale (0-100), and the target property (AI-likeness), plus the method in parentheses. It is immediately clear what the tool does; only sibling differentiation is absent, and the sole sibling remove_watermark is unrelated.

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

Usage Guidelines2/5

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

The second sentence, 'Free, no account,' is a practical prerequisite but not usage guidance. Nothing says when to reach for this tool versus alternatives, what input types are appropriate, or any when-not-to-use condition.

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