Skip to main content
Glama

ADS Beast

creative_copy_humanize

Read-only

Scores a text 0-100 for signs of machine writing, lists the markers found and returns a cleaned version. It never invents facts.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to check or use.
surfaceNoad_copy, prose, report or raw.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds value beyond that: it discloses the three-part output (score, marker list, cleaned text) and a behavioral guarantee that the rewrite 'never invents facts', which is exactly the kind of context annotations cannot convey. It omits thresholds, length limits, and whether the cleaned version may be identical to the input.

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 sentences, front-loaded with the core behavior and followed by the no-fabrication guarantee. No filler, no restatement of the tool name.

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?

A simple two-parameter read-only tool with no output schema, and the description explains all three return components, which is the main gap it needed to fill. Minor omissions remain around how 'surface' affects results and what the 0-100 scale means in practice.

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%, so both parameters are already documented and the baseline is 3. The description adds nothing about the 'surface' enum (ad_copy, prose, report, raw) or how it changes scoring/rewriting, so it does not exceed the baseline.

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 specific verbs and resource: scores text 0-100 for machine-writing markers, lists markers, and returns a cleaned version. That is concrete and distinguishable from generation siblings. It does not name or contrast any sibling (e.g., creative_copy_generate), so it falls short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives such as creative_copy_generate or creative_banner_quality_check, and no prerequisites. Usage is only inferable from the stated purpose.

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.