Skip to main content
Glama
malamutemayhem

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

copypass_run

Run a deterministic CopyPass review of AI-generated copy to get evidence-backed findings, scope boundaries, disclaimers, and a structured proof receipt.

Instructions

Start a deterministic CopyPass review for caller-provided AI-generated copy. Returns evidence-backed copy findings, scope boundaries, disclaimer text, a structured copypass_receipt_v1 proof envelope, and optional CopyRoom exact-copy receipt.

Input Schema

NameRequiredDescriptionDefault
goalNoOptional goal for the copy, such as clarity, conversion, or trust.
channelNoOptional surface label such as homepage_hero, pricing_section, or onboarding_email.
profileNoReview depth label for this scoped run. Defaults to smoke.
audienceNoOptional intended audience for the copy.
copy_textNoThe AI-generated copy to review. Optional when copyroom_source_packet is provided; exact-copy verification compares this text byte-for-byte against the packet.
copyroom_requiredNoSet true when exact fidelity matters. Missing copyroom_source_packet returns COPYROOM_MISSING instead of a run with a null receipt.
copyroom_source_packetNoExact source packet for CopyRoom fidelity work. Use this instead of retyping source text when code, prompts, labels, tables, documents, or user-provided text must stay exact.
copyroom_output_pointerNoPointer to the intended output artifact for the CopyRoom receipt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.11
    • changedInput schema / properties / copy_text / description
      Previous value: -"The AI-generated copy to review."New value: +"The AI-generated copy to review. Optional when copyroom_source_packet is provided; exact-copy verification compares this text byte-for-byte against the packet."
    • addedInput schema / properties / copyroom_output_pointer
      Added value: +{
+  "description": "Pointer to the intended output artifact for the CopyRoom receipt.",
+  "type": "string"
+}
    • addedInput schema / properties / copyroom_required
      Added value: +{
+  "description": "Set true when exact fidelity matters. Missing copyroom_source_packet returns COPYROOM_MISSING instead of a run with a null receipt.",
+  "type": "boolean"
+}
    • addedInput schema / properties / copyroom_source_packet
      Added value: +{
+  "additionalProperties": false,
+  "description": "Exact source packet for CopyRoom fidelity work. Use this instead of retyping source text when code, prompts, labels, tables, documents, or user-provided text must stay exact.",
+  "properties": {
+    "encoding": {
+      "description": "CopyRoom v1 encoding. Defaults to utf8.",
+      "enum": [
+        "utf8"
+      ],
+      "type": "string"
+    },
+    "newline_policy": {
+      "description": "CopyRoom v1 newline policy. Defaults to preserve.",
+      "enum": [
+        "preserve"
+      ],
+      "type": "string"
+    },
+    "source_id": {
+      "description": "Stable source identifier.",
+      "type": "string"
+    },
+    "source_pointer": {
+      "description": "Pointer to the CopyRoom/source location.",
+      "type": "string"
+    },
+    "text": {
+      "description": "Exact source text to copy or verify.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source_id",
+    "source_pointer",
+    "text"
+  ],
+  "type": "object"
+}
    • changedInput schema / properties / profile / description
      Previous value: -"Reserved for later evaluator depth. Defaults to smoke."New value: +"Review depth label for this scoped run. Defaults to smoke."
    • changedInput schema / required
      Previous value: -[
-  "copy_text"
-]New value: +[]
  2. Addedv0.1.9
  3. Removed
  4. Addedv0.1.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful traits: the run is described as deterministic and the output includes findings, scope boundaries, disclaimers, a proof envelope, and an optional exact-copy receipt. It says nothing about whether the run persists state, is idempotent, requires auth, or how failure modes other than the schema's COPYROOM_MISSING behave.

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?

Two sentences, zero filler, purpose stated first and the return payload second. The second sentence is a dense list, but every item is distinct output the caller cares about.

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

Completeness3/5

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

For an 8-parameter tool with a nested object and no output schema or annotations, the description covers purpose and the shape of the result reasonably well but omits how it relates to copypass_status, whether runs are persisted and retrievable, and any precondition/error expectations. Adequate but with clear gaps.

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 description coverage is 100%, so all eight parameters are already documented with enums and defaults in the schema; the description adds no parameter-level syntax or semantics beyond the fact that the copy is 'caller-provided'. Baseline 3 per the high-coverage rule.

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?

The description names a specific verb and resource ('Start a deterministic CopyPass review') and scopes the input to 'caller-provided AI-generated copy', so an agent knows exactly what this tool does. It does not, however, distinguish itself from the sibling copypass_status tool, leaving the agent to infer the split.

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 statement of when to run this versus copypass_status or the related pass-family tools (testpass_run, uxpass_run, etc.). The only conditional behavior ('copyroom_required') lives in the schema, not the description, so no usage guidance is offered at the description level.

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