Docs/Skills/Grammar Check Skill

Grammar Check Skill

Check grammar and spelling

OperationalCredits 20 per callp50 450msText Processing

Overview

Pass any raw string in the request body to scan it for grammatical issues and misspelled words. The response states whether modifications were needed, counts the total issues found, and provides the fully revised text. Subscribers on paid plans also receive character offsets, violated rules, and specific replacement suggestions for each error.

Live Test Grammar Check Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as GrammarCheckSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "GrammarCheckSkill",
  "arguments": {
    "text": "This is a sample text with a grammatical error."
  }
}

You do not name the tool yourself; the model picks it. Asking about This is a sample text with a grammatical error. in the terms this skill covers is enough for it to reach for GrammarCheckSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
textRequiredstringThe text you want to check for grammatical and spelling errors
length 0–50000

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "modified": true,
    "corrected": "The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy",
    "errorCount": 3,
    "corrections": [
      {
        "rule": "repeated_word",
        "message": "Did you mean to repeat the word \"The\"?",
        "position": {
          "start": 0,
          "end": 7
        },
        "suggestions": [
          "The"
        ]
      },
      {
        "rule": "spelling",
        "message": "Did you mean \"because\"?",
        "position": {
          "start": 67,
          "end": 74
        },
        "suggestions": [
          "because"
        ]
      },
      {
        "rule": "spelling",
        "message": "Did you mean \"puppy\"?",
        "position": {
          "start": 92,
          "end": 101
        },
        "suggestions": [
          "puppy"
        ]
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
modifiedbooleantrueIndicates whether any grammar or spelling errors were found
correctedstringThe pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppyThe text with grammar and spelling corrections applied
errorCountnumber3Total number of errors found in the text
correctionsPremiumarray[3]Array of corrections with details about each error
corrections.0.rulePremiumstringrepeated_wordThe grammar rule that was violated
corrections.0.messagePremiumstringDid you mean to repeat the word "The"?Description of the error
corrections.0.positionPremiumobject{…}Start and end position of the error in the text
corrections.0.position.startPremiumnumber0Character offset where the flagged text begins
corrections.0.position.endPremiumnumber7Character offset where the flagged text ends
corrections.0.suggestionsPremiumarray["The"]Suggested corrections for the error

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This skill is not part of VerveKit. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 20 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Content Management Proofing
Flag grammar mistakes in submitted blog drafts and substitute corrected sentences before publishing articles to readers.
Customer Support Messaging
When agents write replies in ticketing desks, the system uses the error count to warn them of uncorrected typos.
Resume Intake Screening
Job portals scan cover letters during applicant uploads, noting whether the text was modified to preserve clean candidate profiles.
Student Essay Feedback
Learning management platforms pass student submissions to display the number of errors and return properly formatted text.

Other ways to use Grammar Check Skill

Set up Grammar Check Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Text Processing:

Was this page helpful?