Aisma

Check credits

get_account

Read-onlyIdempotent

Your Aisma credit balance and every limit of this connection with what is left: credits this month and per edit, edit starts an hour, edits at once, uploads an hour and the account's daily uploads (Library sources count as uploads). The account owner changes the limits in Aisma (manageUrl). Credits are bought in the Aisma app.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`limits`	Yes	Every limit of this key or connection and of the account, keyed by the names limit refusals use.
`balance`	Yes
`manageUrl`	No
`credential`	Yes
`checkoutUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedNov 3, 2026
- addedOutput schema / properties / credential / properties / kind
```
Added value: +{
+  "enum": [
+    "key",
+    "connection"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / credential / properties / monthlyCreditCap / description
```
Added value: +"Null: no monthly cap."
```
- changedOutput schema / properties / credential / properties / monthlyCreditCap / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- addedOutput schema / properties / limits / additionalProperties / properties / adjustable
```
Added value: +{
+  "description": "Whether the account owner can change it in Aisma.",
+  "type": "boolean"
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / ceiling
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / custom
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / default
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / max / description
```
Added value: +"Null: no limit."
```
- changedOutput schema / properties / limits / additionalProperties / properties / max / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- addedOutput schema / properties / limits / additionalProperties / properties / remaining
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / resetSeconds
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / resetsAt
```
Added value: +{
+  "format": "date-time",
+  "type": "string"
+}
```
- addedOutput schema / properties / limits / additionalProperties / properties / used
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / limits / additionalProperties / required
```
Added value: +[
+  "max",
+  "adjustable"
+]
```
- addedOutput schema / properties / limits / description
```
Added value: +"Every limit of this key or connection and of the account, keyed by the names limit refusals use."
```
- addedOutput schema / properties / limits / propertyNames
```
Added value: +{
+  "enum": [
+    "monthly_credits",
+    "job_credits",
+    "start",
+    "active",
+    "upload",
+    "quote",
+    "read",
+    "webhook",
+    "daily_videos",
+    "daily_photos"
+  ]
+}
```
- addedOutput schema / properties / manageUrl
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
First observedOct 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavior context beyond annotations: it enumerates the limits returned, clarifies that Library sources count as uploads, notes that the account owner changes limits via Aisma manageUrl, and explains where credits are purchased.

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 main purpose and stays compact despite enumerating several limits. Some phrasing is dense and slightly awkward, but every sentence contributes useful account or limit context.

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?

For a zero-parameter read tool with annotations and an output schema, the description provides enough context about what is returned and how limits are managed. The exact response shape is appropriately left to the output schema.

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?

There are no parameters, so there is no parameter semantics burden; the schema confirms an empty object with 100% description coverage. The baseline for a zero-parameter tool is 4.

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?

The description states that this returns the Aisma credit balance and every connection limit with remaining amounts, including monthly credits, per-edit credits, edit-start rate, concurrent edits, and upload limits. This is a specific resource and scope, though it does not explicitly contrast itself with any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied: check credits and limits. However, it does not explicitly say when to use this versus alternatives or when not to use it, and the sibling tools do not include an obvious duplicate that would clarify the routing.

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

All Aisma tools Inspect

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.