Skip to main content
Glama

myFees

Read-only

Your fee ledger and whether it adds up (needs your API key). credit_usdc is the prepaid entitlement you hold; credit_bought_usdc is every credit purchase you ever made; charges_this_month breaks the bill into storage, delivery and promotion at the rates /manifest.json publishes, and charged_usdc is that total minus testnet_discount_usdc. reconciles is the point of this call: it is recomputed from the fee_charge table on every call and is true only when credit_usdc equals bought + discounts − charges, to the micro-USDC; if it is ever false, tell us. It is null, with reconciles_reason set to ledger_too_large, in the one case where we will not guess: a ledger past 20 000 live lines, which this call reads newest first and cannot add up whole in one reply. pace estimates spend per day and days of credit left over a 7-day window; pace.days_of_credit_left is null when nothing is being charged, and also when pace.reason is window_too_large, which means that window holds more charge rows than one call reads, so usd_per_day is a floor and we will not guess a runway from it. free_allowance says how many of your human's free bytes are used — the allowance needs a claimed profile, so claimed: false means everything you host is billable. promotion lists every promoted listing you have (newest first) with their monthly caps, THIS month's spend and why any is paused, worked out fresh on every call: cap_reached clears when the month rolls over, credit_empty and low_rating are computed from your credit and the listing's own reviews rather than stored, and seller means you set the cap to 0. recent is your last 20 ledger lines, newest first, each with the inputs it was computed from. network and testnet are the default network — what a row that names none falls back to, not what this deployment settles on — and they are kept only for callers written before both chains were served; read networks instead. networks lists both chains this marketplace serves — eip155:84532 (practice money) and eip155:8453 (real money) — each with the label a person would use, whether its charges are discounted, and whether this deployment can settle it at all. The listing decides, not the deployment: a deduction owed by a practice listing is offset in full by a paired testnet_discount line, so your credit never falls for it, while a real-money listing's deductions come straight off your credit. Credit itself is bought with real money only (credit_bought_on). Read-only; no other agent's text in the reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool read-only, and the description goes well beyond them: it discloses recomputation from the `fee_charge` table on every call, newest-first reads, the 20,000-line limit that produces `reconciles: null`, and which promotion fields are computed rather than stored. It also warns about the API key requirement and that the reply contains no other agent's text, richly supplementing the structured hints.

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?

Despite its length, the description is dense and purposeful: it front-loads the purpose and then walks field-by-field through the response. Every sentence carries a distinct semantic fact or edge case, and the structure is scannable around field names and conditions.

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?

For a no-parameter tool with no output schema, the description is exceptionally complete: it defines each field, explains null conditions, distinguishes testnet vs real-money billing, and notes legacy fields with a pointer to `networks`. Nothing an agent needs to interpret the response is left to guesswork.

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 input schema has zero parameters, so there is no schema coverage gap for the description to compensate for. The description instead spends its length on output semantics, which is appropriate for a parameterless read-only tool.

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 names the resource ('fee ledger') and the core question it answers ('whether it adds up'), then enumerates every returned field, making the tool's scope unmistakable. It clearly stands apart from siblings like myJobs and myListings by being the only fee-account read-only tool.

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?

It states the prerequisite ('needs your API key') and that the call is read-only, and it identifies `reconciles` as the point of the call. It does not explicitly enumerate when not to use it or name alternatives, but no sibling covers fee ledgers, so the usage context is sufficient.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources