Aident AI

Manage Aident billing

billing

Destructive

Use action=balance only when the user asks to inspect credits; do not preflight credit-consuming work. Use action=plans to compare live subscriptions before recommending a purchase. Create checkout only after the user chooses. Use refund-quote before refund, then pass its quote ID with explicit confirmation. Portal, invoices, and trial-status actions manage the existing account.

Input Schema

Name	Required	Description	Default
`flow`	No	Customer portal flow
`limit`	No	Maximum invoice count
`action`	No	Check balance, compare plans, or manage billing for the current account	balance
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`surface`	No	Plan catalog: loadout or aident	loadout
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`trialCode`	No	Trial invite code for checkout
`refundQuoteId`	No	Quote ID returned by the refund-quote action
`priceLookupKey`	No	Plan returned by the plans action
`refundConfirmation`	No	Required confirmation for a Credit Boost refund

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / priceLookupKey / enum

Previous value: -[
-  "free",
-  "basic_monthly",
-  "basic_yearly",
-  "pro_monthly",
-  "pro_yearly",
-  "max_monthly",
-  "max_yearly",
-  "loadout_basic_monthly",
-  "loadout_pro_monthly",
-  "loadout_team_monthly",
-  "loadout_credit_boost_950",
-  "loadout_credit_boost_1950",
-  "loadout_credit_boost_5000",
-  "loadout_credit_boost_950_subscriber",
-  "loadout_credit_boost_1950_subscriber",
-  "loadout_credit_boost_5000_subscriber",
-  "loadout_credit_boost_1000",
-  "loadout_credit_boost_2000",
-  "loadout_credit_boost_5000_v2",
-  "loadout_credit_boost_10000",
-  "loadout_credit_boost_20000",
-  "loadout_credit_boost_1000_subscriber",
-  "loadout_credit_boost_2000_subscriber",
-  "loadout_credit_boost_5000_v2_subscriber",
-  "loadout_credit_boost_10000_subscriber",
-  "loadout_credit_boost_20000_subscriber"
-]New value: +[
+  "free",
+  "basic_monthly",
+  "basic_yearly",
+  "pro_monthly",
+  "pro_yearly",
+  "max_monthly",
+  "max_yearly",
+  "loadout_basic_monthly",
+  "loadout_pro_monthly",
+  "loadout_team_monthly",
+  "loadout_team_99_monthly",
+  "loadout_credit_boost_950",
+  "loadout_credit_boost_1950",
+  "loadout_credit_boost_5000",
+  "loadout_credit_boost_950_subscriber",
+  "loadout_credit_boost_1950_subscriber",
+  "loadout_credit_boost_5000_subscriber",
+  "loadout_credit_boost_1000",
+  "loadout_credit_boost_2000",
+  "loadout_credit_boost_5000_v2",
+  "loadout_credit_boost_10000",
+  "loadout_credit_boost_20000",
+  "loadout_credit_boost_1000_subscriber",
+  "loadout_credit_boost_2000_subscriber",
+  "loadout_credit_boost_5000_v2_subscriber",
+  "loadout_credit_boost_10000_subscriber",
+  "loadout_credit_boost_20000_subscriber"
+]

Changed4 schema fields changedSep 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 28, 2026

changedInput schema / properties / priceLookupKey / enum

Previous value: -[
-  "free",
-  "basic_monthly",
-  "basic_yearly",
-  "pro_monthly",
-  "pro_yearly",
-  "max_monthly",
-  "max_yearly",
-  "loadout_basic_monthly",
-  "loadout_pro_monthly",
-  "loadout_team_monthly",
-  "loadout_credit_boost_950",
-  "loadout_credit_boost_1950",
-  "loadout_credit_boost_5000",
-  "loadout_credit_boost_950_subscriber",
-  "loadout_credit_boost_1950_subscriber",
-  "loadout_credit_boost_5000_subscriber"
-]New value: +[
+  "free",
+  "basic_monthly",
+  "basic_yearly",
+  "pro_monthly",
+  "pro_yearly",
+  "max_monthly",
+  "max_yearly",
+  "loadout_basic_monthly",
+  "loadout_pro_monthly",
+  "loadout_team_monthly",
+  "loadout_credit_boost_950",
+  "loadout_credit_boost_1950",
+  "loadout_credit_boost_5000",
+  "loadout_credit_boost_950_subscriber",
+  "loadout_credit_boost_1950_subscriber",
+  "loadout_credit_boost_5000_subscriber",
+  "loadout_credit_boost_1000",
+  "loadout_credit_boost_2000",
+  "loadout_credit_boost_5000_v2",
+  "loadout_credit_boost_10000",
+  "loadout_credit_boost_20000",
+  "loadout_credit_boost_1000_subscriber",
+  "loadout_credit_boost_2000_subscriber",
+  "loadout_credit_boost_5000_v2_subscriber",
+  "loadout_credit_boost_10000_subscriber",
+  "loadout_credit_boost_20000_subscriber"
+]

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / priceLookupKey / enum

Previous value: -[
-  "free",
-  "basic_monthly",
-  "basic_yearly",
-  "pro_monthly",
-  "pro_yearly",
-  "max_monthly",
-  "max_yearly",
-  "loadout_basic_monthly",
-  "loadout_pro_monthly",
-  "loadout_credit_boost_950",
-  "loadout_credit_boost_1950",
-  "loadout_credit_boost_5000"
-]New value: +[
+  "free",
+  "basic_monthly",
+  "basic_yearly",
+  "pro_monthly",
+  "pro_yearly",
+  "max_monthly",
+  "max_yearly",
+  "loadout_basic_monthly",
+  "loadout_pro_monthly",
+  "loadout_team_monthly",
+  "loadout_credit_boost_950",
+  "loadout_credit_boost_1950",
+  "loadout_credit_boost_5000",
+  "loadout_credit_boost_950_subscriber",
+  "loadout_credit_boost_1950_subscriber",
+  "loadout_credit_boost_5000_subscriber"
+]

Changed1 schema field changedAug 14, 2026

changedInput schema / properties / priceLookupKey / enum

Previous value: -[
-  "free",
-  "basic_monthly",
-  "basic_yearly",
-  "pro_monthly",
-  "pro_yearly",
-  "max_monthly",
-  "max_yearly",
-  "loadout_basic_monthly",
-  "loadout_credit_boost_950",
-  "loadout_credit_boost_1950",
-  "loadout_credit_boost_5000"
-]New value: +[
+  "free",
+  "basic_monthly",
+  "basic_yearly",
+  "pro_monthly",
+  "pro_yearly",
+  "max_monthly",
+  "max_yearly",
+  "loadout_basic_monthly",
+  "loadout_pro_monthly",
+  "loadout_credit_boost_950",
+  "loadout_credit_boost_1950",
+  "loadout_credit_boost_5000"
+]

First observedAug 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag the tool as destructive and not read-only, and the description adds real behavior beyond that: a mandatory quote-then-refund sequence, an explicit confirmation gate before refund, and a prohibition on preflighting credit-consuming work. It does not say which of the eight actions actually mutate state (invoices and balance are clearly reads) or what subscription_cancel/stop_cancel does to the account, so the destructive flag stays under-explained.

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?

Four tight sentences, no filler, and the guardrail against preflighting balance is front-loaded. It loses a point for having no framing sentence, so the reader hits action-specific rules before learning what the tool as a whole is.

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

Completeness3/5

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

For a 10-parameter, 8-action dispatcher with no output schema, the usage sequencing is well covered but key context is missing: no indication of what each action returns, which actions are read-only, or how the portal/subscription flows and surface selection work. Annotations only carry a blanket destructive flag, so the description should do more to partition safe reads from mutations.

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 baseline is 3, but the description earns more by linking parameters across calls: the refundQuoteId must come from a prior refund-quote action and refund requires 'explicit confirmation', which corresponds to the const refundConfirmation. It still says nothing about limit, surface, trialCode, or flow, leaving those to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Each sentence names a concrete action and its resource: balance 'to inspect credits', plans 'to compare live subscriptions', checkout, refund, and the portal/invoices/trial-status group 'manage the existing account'. The tool's overall role as an account billing dispatcher is therefore clear, but there is no opening sentence stating the tool's top-level purpose and no differentiation from siblings such as affiliate or vault.

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 gives explicit when-to-use and when-not-to-use rules: 'Use action=balance only when the user asks to inspect credits; do not preflight credit-consuming work' and 'Create checkout only after the user chooses'. It also prescribes ordering for the risky path: 'Use refund-quote before refund, then pass its quote ID with explicit confirmation'.

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

All Aident AI tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?