pdfops-mcp

Official

by pdfops

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Check PDFops quota

pdfops_usage

Read-onlyIdempotent

Check your PDFops API quota before batch processing to confirm available headroom. Shows tier, limit, used, remaining, billing period, and reset time.

Instructions

Check the current PDFops API quota for the configured key: tier, limit, used, remaining, the billing period, and the reset timestamp. Read-only and safe to call before a batch to confirm there is headroom. Requires PDFOPS_API_KEY.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tier`	Yes	Plan name, e.g. free
`used`	Yes
`limit`	Yes	Calls allowed in the current period
`period`	Yes	Billing period the counts belong to, YYYY-MM
`remaining`	Yes
`resets_at`	Yes	ISO 8601 timestamp when used resets to 0

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.2Sep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "limit": {
+      "description": "Calls allowed in the current period",
+      "type": "integer"
+    },
+    "period": {
+      "description": "Billing period the counts belong to, YYYY-MM",
+      "type": "string"
+    },
+    "remaining": {
+      "type": "integer"
+    },
+    "resets_at": {
+      "description": "ISO 8601 timestamp when used resets to 0",
+      "type": "string"
+    },
+    "tier": {
+      "description": "Plan name, e.g. free",
+      "type": "string"
+    },
+    "used": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "tier",
+    "limit",
+    "used",
+    "remaining",
+    "period",
+    "resets_at"
+  ],
+  "type": "object"
+}

First observedv0.2.0Aug 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive; the description adds a prerequisite ('Requires PDFOPS_API_KEY') and clarifies that it performs no mutation and is safe for pre-batch checks. This meaningfully supplements the annotation metadata.

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?

Two dense sentences: the first states the resource and expected return fields, and the second covers safety, usage timing, and configuration requirements. There is no filler or redundant restatement.

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?

Given zero parameters, rich annotations, and an output schema, the description supplies all necessary extra context: what to expect, when to call it, and the required environment variable. Nothing important is missing.

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?

The input schema is empty with 100% coverage, so the baseline is 4 for zero parameters. The description adds no parameter details, but none are needed.

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?

The description names a specific verb ('Check'), a specific resource ('current PDFops API quota for the configured key'), and enumerates the returned fields (tier, limit, used, remaining, billing period, reset timestamp). This clearly separates it from sibling tools like pdf_fill and pdf_merge, which are about document operations.

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?

It gives an explicit use case: 'safe to call before a batch to confirm there is headroom.' It does not explicitly name sibling alternatives or state when not to use the tool, but the context is strong enough for an agent to select it correctly.

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

Deploy Server