Skip to main content
Glama
Sign In
docrenders-mcp

docrenders-mcp

by JWhist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_usage

Check your current period render usage to see how many documents you've generated with DocRenders.

Instructions

Check the current period render usage for the authenticated DocRenders account.

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 observedv0.4.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It describes a read-only operation ('check') and is non-destructive. However, it does not disclose additional behavioral traits like rate limits, data freshness, or specific usage metrics returned.

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?

One succinct sentence with no wasted words. The key information is front-loaded and immediately actionable.

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

Completeness3/5

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

While the description adequately states the tool's purpose, it lacks details on what the return value contains (e.g., usage numbers, limits) since there is no output schema. For a simple zero-parameter tool, this is acceptable but incomplete.

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 tool has zero parameters and schema coverage is 100%, so the description does not need to add parameter details. Per guidelines, 0 parameters gets baseline 4.

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 clearly states what the tool does: 'Check the current period render usage for the authenticated DocRenders account.' It uses specific verb 'check' and resource 'render usage', distinguishing it clearly from sibling tools focused on templates and rendering.

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?

The description implies usage for viewing account usage stats. It clearly identifies the context (authenticated account, current period) but does not explicitly state when not to use it or mention alternatives. Given siblings, the use case is clear enough.

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