Skip to main content
Glama
Sign In

fermi

by io.github.Kromatic-Innovation
OverviewDiscussionsAdmin

Check your account, credits and free estimates left

check_account_and_credits
Read-onlyIdempotent

Reports who you are to Fermi and what you can spend: whether you are using Fermi without an account or with one, your credit balance or free estimates left today, and what each tier costs. Use this before a paid estimate to check the price or balance, after one to see what is left, or when the user asks about credits, free estimates or pricing.

Returns billing (principal "anonymous" or "account", how you authenticated, credit_balance, anonymous_estimates_remaining_today and anonymous_quota_resets_at), tiers (credit_cost, delivery "sync" or "async" and whether it is available without an account, per tier), price_per_credit_usd, and recent_transactions (the account's last 10 credit movements; null without an account).

Cost: free. Checking never spends credits and never uses up a free estimate.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Fermi API key. Omit it to ask about your connector's signed-in account, or about your free allowance without an account.

Output Schema

NameRequiredDescriptionDefault
tiersNoEach tier's price and availability.
billingNoWho this call was billed to and what is left. Present on every Fermi result.
recent_transactionsNoThe account's last 10 credit movements (entry_type, amount, request_id, created_at); null without an account.
price_per_credit_usdNoWhat one credit costs to buy, in US dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the check is free, never spends credits, and never consumes a free estimate — exactly the reassurance an agent needs before calling it repeatedly. The return-field enumeration partially duplicates the output schema, which keeps it from a 5.

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?

Front-loaded: purpose and usage come before the return-value detail, and the free/no-spend guarantee is placed last for emphasis. The middle paragraph enumerating billing, tiers, price_per_credit_usd and recent_transactions is largely redundant with the output schema and inflates the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema already exists, so the detailed return-field listing is not required, but nothing an agent needs is missing: it covers anonymous vs authenticated behavior, null transactions without an account, cost, and use cases. Complete and slightly over-specified rather than deficient.

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?

Only one optional parameter, and schema coverage is 100%, so the baseline is 3. The description earns above baseline by foregrounding the anonymous-vs-account distinction that api_key selects, framing the parameter's meaning rather than restating it, though it never names the parameter or its omission behavior explicitly.

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 opening clause states a specific verb and resource: it reports identity and spendable balance (credits, free estimates, tier pricing). It is clearly distinct from the estimation siblings (get_estimate_result, list_my_estimates) and from buy_credits, which it complements rather than duplicates.

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?

Explicit trigger conditions are given: before a paid estimate to check price or balance, after one to see what is left, or when the user asks about credits/free estimates/pricing. This is when-to-use guidance mapped to concrete agent decision points rather than vague context.

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

All fermi 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