Storefinch

Show plan and usage

get_account

Read-onlyIdempotent

Show the plan behind the current API key: its monthly limits, calls and export rows used and remaining, when usage resets, and links to upgrade or manage billing. Call it before a large export or after a quota error. Free: it doesn't count against the quota.

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_account"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	'trial' is the free plan; 'pro' is the paid plan.
`limits`	Yes
`resets_at`	Yes	When monthly usage resets (UTC).
`billing_url`	Yes	Manage or cancel a subscription.
`upgrade_url`	No	Where to upgrade; absent on the paid plan.
`data_release`	No
`quota_remaining`	Yes
`used_this_month`	Yes	Calls and export rows used since the 1st (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely non-obvious fact — the call is free and does not count against the quota — but says nothing about rate limits or freshness/caching of the usage figures.

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 short sentences, front-loaded with the resource and payload, followed by trigger conditions and the cost caveat. Every sentence carries distinct information; nothing is restated from the title or annotations.

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?

An output schema exists, so return shape need not be explained, and the description still previews the key fields. For a zero-parameter, read-only tool this covers everything an agent needs to decide to call it and to interpret the result.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the key is inferred from the request context ('the current API key') rather than passed in.

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 ('Show the plan behind the current API key') and enumerates exactly what is returned: monthly limits, calls and export rows used/remaining, reset time, and billing links. No sibling tool covers account/billing state, so the scope is unambiguous.

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?

Gives two concrete triggers: 'before a large export' and 'after a quota error'. That is clear when-to-use guidance, but it does not name alternatives or state when-not to call it (e.g. caching the result rather than polling).

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

All Storefinch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?