Skip to main content
Glama
Sign In
Prufa

Prufa

Official
by prufa-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

prufa_get_usage

Check workspace credit usage and trial state before a costly run. Get available/included credits and an upsell block if credits are low.

Instructions

Get this workspace's credit usage (available/included) plus trial state and, when relevant, an upsell block. Use before a costly run to check the balance and relay the message_for_human if credits are low.

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": "prufa_get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A4.8/5.0
Behavior4/5

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

No annotations provided, but the description uses 'Get' which strongly implies a read-only, non-destructive operation. It does not explicitly state side effects or safety, but the verb is sufficient.

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?

Two short sentences, no fluff. First sentence states the output, second gives usage guidance. Front-loaded with essential information.

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?

No output schema exists, but description lists all return components (credit usage, trial state, upsell block, message_for_human). Combined with usage context, it provides a complete picture for the agent.

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?

No parameters exist, so schema coverage is 100% trivially. The description adds meaning by detailing the output fields (credit usage, trial state, upsell block), providing context beyond the empty schema.

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 the tool returns workspace credit usage, trial state, and upsell block. It distinguishes from siblings like prufa_buy_credits and prufa_billing_portal by focusing on read-only usage info.

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?

Explicitly advises to use before costly runs to check balance and relay message_for_human if low. This provides clear context for when to invoke the tool.

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