Skip to main content
Glama
Sign In

Framevine

by com.framevine
OverviewDiscussionsAdmin

Get account usage

get_account_usage
Read-onlyIdempotent

Get the user's Framevine account usage in one call. credits: the current balance (total, plus subscription and purchased credits), how many credits they have used today and this month, and how many credits this connection can spend right now (availableToSpendCredits): the lower of the balance and what is left of the daily limit the user set for this app. connectionDailyLimitCredits and connectionRemainingTodayCredits are null when the user chose no daily limit. storage: their plan, used, total and available bytes, percent used, how many days files are kept, and a breakdown into uploads, generations and hidden files. Pass threadId to also get threadSpend: what that thread's generations cost (the total credits used, and for each generation, newest first, its operation, model, status and the credits charged, refunded and net). All of these are positive numbers of credits spent: totalCreditsUsed and netCredits are net of refunds (charged minus refunded). Call this first to check the user can afford generations and has room for large uploads or video, or after a purchase to confirm credits arrived. Use estimate_cost to see whether one specific generation will fit.

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

Input Schema

NameRequiredDescriptionDefault
limitNoWith threadId: maximum number of generations to list in threadSpend (default 50).
threadIdNoOptional thread id, from list_threads. Adds threadSpend to the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations establish that this is a read-only, idempotent, non-destructive call. The description adds substantial behavior beyond annotations: it explains credit balance sources, available-to-spend logic, null daily-limit fields, storage breakdowns, thread spend ordering, and net-of-refund semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then details return values because there is no output schema. It is dense but mostly earns its length; slightly more structure could make the long field list easier to scan.

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 no output schema, the description carries the burden of explaining return values, and it does so comprehensively for credits, storage, and optional thread spend. It also covers the key usage context needed to decide whether to call it.

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?

Schema coverage is 100%, so the `limit` parameter is already documented in the schema. The description still adds meaning for `threadId` by explaining what `threadSpend` contains and how its values should be interpreted, though it does not discuss `limit` itself.

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 states a specific verb and resource: get the user's Framevine account usage in one call. It clearly distinguishes the tool from the sibling cost-estimation tool by naming `estimate_cost` for a different purpose.

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?

It explicitly says when to call this tool: first, to check whether the user can afford generations and has room for uploads/video, or after a purchase to confirm credits arrived. It also names `estimate_cost` as the alternative when checking one specific generation.

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

All Framevine toolsInspect
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