Skip to main content
Glama
getscreenshot-mcp

getscreenshot-mcp

Official
by rasterwise

Get usage

get_usage
Read-only

Check remaining monthly screenshot quota, plan limit, and reset date before large capture batches or after quota errors; note that each check consumes one screenshot.

Instructions

Report how many screenshots the configured API key has used this month, the plan's monthly limit, how many are left and when the quota resets. Use it before a large batch of captures or when a capture fails with a quota error. This check itself costs 1 screenshot of the quota, so do not call it routinely.

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

Output Schema

NameRequiredDescriptionDefault
usedYesScreenshots used in the current period.
limitYesScreenshots included per period on this plan.
periodYes
remainingYes
resets_onYesDate (UTC) the monthly quota next resets.
percent_usedYes
quota_restart_dateYes`quotaRestartDate` exactly as the API reports it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Discloses a trait annotations cannot express: the call itself consumes 1 screenshot of the quota, which also explains why idempotentHint is false. It also names the scope binding (the configured API key) and the monthly reset window, far beyond the readOnly/destructive flags supplied.

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?

Three tight sentences ordered by value: what is reported, when to call it, then the non-obvious cost caveat last as a warning. No filler, no restatement of the title, and the cost warning is prominent enough to affect behavior.

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?

The output schema already documents the return shape, so the description focuses on what it must carry: call cost, quota scope, reset timing, and usage conditions. Nothing an agent needs to invoke this correctly is missing.

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

Parameters5/5

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

The tool takes zero parameters and the description correctly introduces no parameter discussion, instead spending its words on scope (the configured API key, this month) that the empty schema cannot convey. Baseline for a parameterless tool is met with no gaps.

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 (report screenshot usage for the configured API key this month) and enumerates exactly what is returned: used count, plan limit, remaining count, and reset time. It is clearly distinct from capture_* and render_* siblings, which produce artifacts rather than reporting quota state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both positive triggers ('before a large batch of captures', 'when a capture fails with a quota error') and an explicit exclusion ('do not call it routinely') with the reason attached. An agent has all it needs to decide when this call is warranted.

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