Skip to main content
Glama

humanize_copy

Read-only

Rewrite audience-facing website, app, and document copy locally while preserving required terms and character limits; invalid or disabled requests return the original text.

Instructions

Rewrite audience-facing copy locally. Submit named text fields, with exact preserve terms and optional max_characters. Keep each call around 300 words total to fit the local time budget. Use plain for app strings/headlines, markdown for document prose. Markdown headings, tables, quotes, and code remain intact; extract headings as plain fields if they need rewriting. Returns originals on validation failure or when the user switches it off. Mechanical checks do not establish factual fidelity; review every accepted rewrite before use.

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": {
      "fields": "<fields>"
    },
    "name": "humanize_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint=false annotations, it discloses local execution with a time budget, markdown structure preservation (headings, tables, quotes, code), and the fallback behavior of returning originals on validation failure or when the user disables it. The closing caveat that mechanical checks do not prove factual fidelity is exactly the kind of trust-boundary information an agent needs.

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 purpose, then format selection, then preservation and failure semantics, then the review caveat — a sensible ordering with each line carrying distinct information. It is dense with seven short lines, but no sentence is filler.

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?

An output schema exists, so return values need not be enumerated, yet the description still covers the failure-mode return ('originals') and the human-review expectation. For a single-nested-parameter rewrite tool, nothing an agent needs to invoke it correctly is missing.

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 description coverage is 0% and the only top-level parameter is a nested array, so the description carries the burden — and it does: named text fields, 'exact' preserve terms, optional max_characters, the plain/markdown enum, and the workaround of extracting headings as plain fields. It does not explain the field 'id' role or the character limits, leaving some gaps.

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 and resource ('Rewrite audience-facing copy') plus the important scope qualifier 'locally', which distinguishes this from a cloud/LLM-service call. It never names the sibling humanizer_status, so an agent must infer the split (rewrite vs. status) from the name alone.

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?

Gives concrete selection guidance for the format choice ('plain for app strings/headlines, markdown for document prose') and a usage constraint ('keep each call around 300 words total to fit the local time budget'). It does not explicitly say when not to use the tool or point to an alternative, which keeps it below a 5.

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

Deploy Server

Other Tools