User Intuition

Get Account

get_account

Read-onlyIdempotent

Read the effective workspace, role, available credit balance, payment method readiness, and incentive limits before a paid action. A payment method on file does not approve spending; use the current estimate and obtain human approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`organization_id`	No	Platform admins only: inspect this organization’s account and billing readiness.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	The effective account, workspace, and payment readiness.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / result / properties / scopes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / organization_id

Added value: +{
+  "description": "Platform admins only: inspect this organization’s account and billing readiness.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed8 schema fields changedSep 30, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / properties / result / properties / billing / properties / available_balance_usd / $ref
```
Removed value: -"#/properties/result/properties/billing/properties/available_credits"
```
- addedOutput schema / properties / result / properties / billing / properties / available_balance_usd / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / billing / properties / currency / $ref
```
Removed value: -"#/properties/result/properties/organization_id"
```
- addedOutput schema / properties / result / properties / billing / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / organization_name / $ref
```
Removed value: -"#/properties/result/properties/organization_id"
```
- addedOutput schema / properties / result / properties / organization_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavioral meaning: a payment method on file does not constitute spending approval, and human approval must be obtained using the current estimate. It does not discuss auth scoping (the platform-admin-only constraint lives in the schema) or rate/refresh characteristics.

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?

Two sentences, zero filler, with the primary purpose front-loaded and the spending-approval caveat immediately after. Every clause earns its place.

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 read-only account/readiness check with a 1-param schema and an output schema, the description covers purpose, trigger, and the key operational caveat, so an agent can call it correctly. The only gap is that it never clarifies its relationship to sibling read tools such as list_organizations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single optional organization_id is already documented as a platform-admin-only scoping parameter. The description adds no syntax or behavioral detail about when to pass it, so the baseline 3 for a schema-documented parameter applies.

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 opens with a precise verb ('Read') and an enumerated resource set (effective workspace, role, credit balance, payment method readiness, incentive limits), so the agent knows exactly what comes back. It does not name or compare against any sibling (e.g. list_organizations), so the differentiation is implied rather than stated.

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 gives a clear situational trigger: call this 'before a paid action', which tells the agent when the tool belongs in a workflow. It stops short of naming alternatives or exclusions (e.g. when list_organizations is preferable), so it is a strong context statement rather than full when/when-not routing.

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

All User Intuition 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?