Skip to main content
Glama

Final check of approved copy

check_final
Read-onlyIdempotent

Validate user-approved final copy by running Whalory checks and returning any remaining findings before publication.

Instructions

Final check of the copy the user approved: runs Whalory's checks and returns any remaining findings, in the same form as lint_text. Call it once when the user approves final copy. If the user turned on Whalory Hub statistics or weekly packets in their own terminal, it also records counts on this computer, never text, of which Whalory checks the user's own edits removed. With statistics, the user chose to send those counts weekly to Whalory's server in Iran; a packet leaves the computer only if the user posts it on GitHub.

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_final"
  }
}

Input Schema

NameRequiredDescriptionDefault
mdNoThe text is Markdown
textYesThe final copy the user approved
formatNoWhalory format id; sets the limits for sentence length, emoji and exclamation marks
channelNoe.g. instagram.caption, linkedin.post (Pro data)
profileNoProfile name (whalory, starter-saas, en/saas), 'auto', or a path inside an allowed root
languageNoauto detects the language per lineauto
playbookNoThe playbook used for the copy, e.g. caption or landing
revisionsNoRevision rounds before the user approved (0: approved as first shown)

Output Schema

NameRequiredDescriptionDefault
langYes
statsYes
issuesYes
passedYes
summaryYes
truncatedNo

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?

Goes well beyond the annotations: it discloses that findings mirror lint_text's output form, that the tool records counts (never text) of checks the user's own edits removed, that this only happens if the user enabled Hub statistics or weekly packets, and that data leaves the machine only if the user posts it on GitHub. This is exactly the privacy/telemetry context an agent needs before invoking a tool whose readOnlyHint could otherwise be misread as "nothing is written anywhere."

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 correctly: purpose, then the call trigger, then the telemetry caveat. The statistics/GitHub sentence is longer than strictly necessary for tool selection, but it carries genuine data-governance information rather than filler.

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?

With an output schema present, return values need no explanation, and the description still points to lint_text as the shape reference. Trigger, side effects, and data flow are all covered; only the draft-versus-final boundary against lint_text is left implicit.

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 (including the format enum's limit-setting role and the channel/profile patterns) are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ("final check of the copy the user approved"), what it returns ("any remaining findings, in the same form as lint_text"), and pins its identity relative to the sibling lint_text. An agent can tell it apart from lint_text by the approval-timing trigger 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?

"Call it once when the user approves final copy" gives a concrete trigger and an invocation-count constraint, and the reference to lint_text implicitly frames the relationship between the two tools. It stops short of stating an explicit when-not (e.g. don't use this on drafts, use lint_text instead), which keeps it out of the top band.

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