Skip to main content
Glama

check_document

Start an originality check of ONE document for the user (PDF, DOCX, DOC, ODT, RTF or TXT, up to 10,000 words). Ask the user's permission first. Returns a token; the check takes 10 to 20 minutes. Send exactly one of content_base64 (with filename), text, or url. Open access has growing waiting times between checks and a small daily limit; never send batches or split documents.

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": {
      "user_confirmed": "<user_confirmed>"
    },
    "name": "check_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoa public link to a PDF, DOCX or TXT file
textNothe document as plain text
filenameNofile name with extension, e.g. thesis.pdf (with content_base64)
content_base64Nothe file, base64-encoded
user_confirmedYestrue only after the user agreed to send the document to OpenPlag Labs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) by disclosing the asynchronous contract: a token is returned and the check takes 10-20 minutes. It also surfaces operational constraints the annotations cannot express — growing waiting times between checks and a small daily limit on open access.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five sentences, each carrying a distinct operational fact (format/size limits, permission, async token and duration, input-mode exclusivity, rate limits). Front-loaded with the action, no filler or restatement of the tool name.

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

Completeness5/5

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

For a 5-parameter asynchronous submission tool with no output schema, the description covers everything needed to call it correctly: accepted formats, size cap, consent requirement, input-mode exclusivity, expected latency, token return, and rate limits. The only unstated element is the polling handoff, which the token-plus-duration sentence strongly implies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine semantic rule not encoded in the schema: send exactly one of content_base64, text, or url, and pair content_base64 with filename. That mutual-exclusivity constraint materially reduces malformed calls.

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 ('Start an originality check of ONE document'), enumerates accepted formats, and caps size at 10,000 words. The 'ONE' capitalization also distinguishes it from any batch-oriented behavior an agent might otherwise assume.

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?

Gives explicit preconditions ('Ask the user's permission first') and explicit prohibitions ('never send batches or split documents'), which is strong when-to-use guidance. The one gap is that it never names the get_check sibling as the way to retrieve results after receiving the token, leaving the follow-up step implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources