Tinify

Get account usage

get_usage

Read-onlyIdempotent

Retrieve current billing-period usage for your Tinify.dev account, including plan, operations included, used, and remaining.

Instructions

Show the Tinify.dev account's current billing-period usage: plan, period, operations included, used, and remaining.

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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`plan`	Yes
`used`	Yes
`included`	Yes
`reserved`	Yes
`remaining`	Yes
`period_end`	Yes
`request_id`	Yes
`period_start`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jul 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already indicate a safe read operation. The description adds context about the specific data returned (plan, period, operations used). No contradictions exist.

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?

Single sentence, 12 words, front-loaded with the verb and resource. Every word earns its place. No redundancy.

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?

With an output schema present, the description needn't detail return structure. It covers the key categories of usage information. Given the tool's simplicity, it is fully complete.

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?

There are no parameters, so the description does not need to add parameter meaning. Per rules, baseline is 4 for 0-param tools. The description focuses on output, which is acceptable.

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 uses the specific verb 'Show' and clearly identifies the resource as 'Tinify.dev account's current billing-period usage', listing key fields (plan, period, operations included, used, remaining). This distinguishes it from sibling image processing tools.

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 does not explicitly state when to use or not use the tool, but sibling tools are all image manipulation, so usage context is clear by contrast. A note on when it is appropriate would improve clarity, but the current level is adequate.

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

Deploy Server