1. Docs
2. /
3. Tool reference
4. /
5. Studio Apps
6. /
7. validateAgainstDocContract

Studio Apps

validateAgainstDocContract

Validate Against Doc Contract

Check a drafted deliverable against the contract it claims, BEFORE filing it.

read

Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "check this against the contract", and it calls validateAgainstDocContract.

Example call

The MCP tools/call params, with the required arguments only.

{
  "arguments": {
    "markdown": "<markdown>"
  },
  "name": "validateAgainstDocContract"
}

Arguments

• markdownstringrequiredThe full deliverable content as it would be filed. Pass JSON text for cloud.gallery/3.
• slugstringoptionalAlias of `typeSlug`. `typeSlug` wins if you send both.
• typeSlugstringoptionalThe contract the deliverable claims, e.g. "builddoc". Case-insensitive. Canonical name; `slug` is accepted too.

Returns

Returns { ok, problems[] }.

Ask for it

The Cloud routes these requests to this verb.

• check this against the contract
• is this a valid builddoc
• validate this gallery collection
• will this pass
• validate my memo

Pair it with

The verbs that finish the job.

• getDocContract
• createPage
• createGallery

Questions

• What does validateAgainstDocContract do?

  Check a drafted deliverable against the contract it claims, BEFORE filing it. It is one of the tools The Cloud MCP server gives every connected AI.

• How do I use validateAgainstDocContract from Claude or ChatGPT?

  Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "check this against the contract", and it calls validateAgainstDocContract.

• Is validateAgainstDocContract safe to let an AI call?

  validateAgainstDocContract is read-only: it changes nothing.

Connect

One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.