GreenlandAI

joules_deficit

Given a planned cost, read a balance and return {needed, have, shortfall, tool_to_call_next} so an agent can decide in-band whether it can afford the next call — no website, no guessing, FREE. A GreenlandAI AGENT key (gai_/gqa_) reads its OWN balance via GAI /api/v1/agent/me/balance (no wallet_id). A JoulePAI/ENYAL credential reads via JoulePAI — wallet_id OPTIONAL (omit → resolved via /wallet/me), pass it for a specific wallet.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cost`	Yes
`wallet_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 14, 2026
- addedInput schema / properties / wallet_id / default
```
Added value: +null
```
- changedInput schema / required
```
Previous value: -[
-  "wallet_id",
-  "cost"
-]New value: +[
+  "cost"
+]
```
First observedSep 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does so well: it reveals the backing endpoints, credential types, wallet_id resolution behavior, and that the operation is a read ('read a balance', 'FREE'). It does not discuss failure modes or rate limits, but the core behavioral surface is disclosed.

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 dense and front-loaded with purpose and return format, followed by credential-specific details. The phrases 'no website, no guessing, FREE' add some rhetorical color but do not seriously bloat the definition.

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 2-parameter tool with no output schema and no annotations, the description covers the essential operation, return keys, credential branches, and wallet_id behavior. Minor gaps like cost units and exact error behavior are not critical for an agent to call it correctly.

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?

Schema coverage is 0%, yet the description compensates fully: cost is explained as the planned cost, and wallet_id is explained as optional, omitted for GAI, auto-resolved via /wallet/me for JoulePAI, or passed for a specific wallet. This adds meaning far beyond the bare 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?

States a specific verb ('read a balance') and a concrete output contract ({needed, have, shortfall, tool_to_call_next}) with an explicit purpose: deciding in-band whether the next call is affordable. This clearly distinguishes it from a plain balance query such as joules_balance.

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?

The description makes the use case explicit: before a planned cost, decide whether the agent can afford the next call, described as 'no website, no guessing'. It gives credential-specific routing (GAI key vs JoulePAI/ENYAL) but does not explicitly name when NOT to use it or compare it to sibling alternatives.

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

All GreenlandAI 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.

Resources

Need Help?