Skip to main content
Glama
Sign In
pdfvera MCP server

pdfvera MCP server

Official
by pdfvera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pdfvera plan and quota

get_usage
Read-only

Check your pdfvera plan and see how many documents of your monthly quota are used. Track remaining capacity to manage invoice conversions.

Instructions

Show the user's pdfvera plan and how many documents of the monthly quota are used.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the read is user-scoped and reports both plan and quota consumption, but says nothing about authentication requirements or what the quota numbers represent (remaining vs. consumed, reset period).

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?

A single front-loaded sentence with no wasted wording. The two outputs (plan, quota usage) are enumerated compactly.

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 zero-argument read tool with no output schema, the description is nearly sufficient: it names the two values returned. A brief note on units or reset window for the quota would close the last gap.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly frames the operation as implicitly scoped to "the user's" account, which is the only contextual qualifier that matters here.

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?

States a specific verb ("Show") and a concrete resource pair ("pdfvera plan" and "documents of the monthly quota are used"). It is unambiguous what the tool returns; it simply doesn't reference the sibling convert_* tools, which is minor since they operate in a clearly different domain.

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: by describing quota consumption the description hints at the pre-conversion check scenario, but it never states when to call this versus anything else, nor any exclusion conditions. No explicit alternatives are named.

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

Deploy Server

Other Tools