Skip to main content
Glama

Lint copy (Persian or English)

lint_text
Read-onlyIdempotent

Check Persian or English copy against Whalory's rules to flag AI tells, puffery, spelling, punctuation, readability, missing facts, and channel limits before publishing.

Instructions

Check Persian or English copy against Whalory's rules (AI tells, puffery, spelling, punctuation, sentence length, readability, brand profile and channel limits). Language is detected per line unless set.

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

Input Schema

NameRequiredDescriptionDefault
mdNoThe text is Markdown
langNoauto detects the language per lineauto
textYesThe copy to check
factsNoBrief or source text; English facts missing from it are flagged
formatNoWhalory format id; sets the limits for sentence length, emoji and exclamation marks
strictNoWarnings also fail the check
channelNoe.g. instagram.caption, linkedin.post (Pro data)
profileNoProfile name (whalory, starter-saas, en/saas), 'auto', or a path inside an allowed root
max_wordsNoSentence length cap
profile_jsonNoInline voice profile (schema v2); wins over profile

Output Schema

NameRequiredDescriptionDefault
langYes
statsYes
issuesYes
passedYes
summaryYes
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world check, so the description is not carrying the safety burden. It adds real behavioral context beyond the annotations by naming the rule categories that get checked and stating that language is detected per line unless set, which tells the agent how mixed-language input is handled.

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?

A single dense sentence with the resource and rule set front-loaded, plus a short qualifier on language detection. The parenthetical list is long but each item is a distinct rule family, so little waste; the only cost is that the long list crowds out any routing guidance.

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 ten-parameter read-only linter with full schema coverage, an output schema, and safety annotations, the description covers what the tool evaluates and how language is resolved. The remaining gap is the absence of any pointer to sibling tools for file-based or final-check workflows.

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% across all ten parameters, so the schema already explains `format`, `channel`, `profile`, `facts`, `strict`, and `md` in detail. The description adds only the per-line language detection note, which duplicates the `lang` schema entry; baseline 3 is appropriate.

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 gives a specific verb+resource ("Check Persian or English copy") and enumerates the rule families applied (AI tells, puffery, spelling, punctuation, sentence length, readability, brand profile, channel limits). It never names or contrasts with siblings like lint_file or check_final, so the agent must infer that this operates on inline text rather than files.

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

Usage Guidelines3/5

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

Usage is only implied: passing `text` for inline copy, with language auto-detection per line. There is no explicit when-to-use vs. when-not guidance, no mention of lint_file for files, and no statement of when check_final should be preferred.

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