ThinAir Data

quota

Read-only

Check current API usage, daily limit, plan name, and upgrade options.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`plan`	Yes
`used`	Yes
`limit`	Yes
`reset_at`	No
`upgrade_url`	No
`schema_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
Changed3 schema fields changedMay 2, 2026
- addedOutput schema / properties / reset_at
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / schema_version
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / upgrade_url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedMay 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "limit": {
+      "type": [
+        "number",
+        "string"
+      ]
+    },
+    "plan": {
+      "type": "string"
+    },
+    "upgrade_url": {
+      "type": "string"
+    },
+    "used": {
+      "type": [
+        "number",
+        "string"
+      ]
+    }
+  },
+  "required": [
+    "used",
+    "limit",
+    "plan"
+  ],
+  "type": "object"
+}

First observedApr 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the response includes plan name and upgrade options, which is genuinely extra context, but it says nothing about auth requirements, whether usage is per-key or account-wide, or rate-limit behavior of this check itself.

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?

A single front-loaded sentence with no filler. Slight redundancy in listing return fields that the output schema will already declare, but the enumeration aids scanning.

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?

No parameters, an output schema that documents the return shape, and annotations covering read-only semantics — the description fills the remaining gap (what domain 'quota' means) and nothing an agent needs to call it is missing.

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?

Zero parameters — baseline 4 per the rubric. The description has nothing to mis-specify and correctly implies no input is needed.

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 names a specific verb-and-resource pairing (check API usage/quota) and enumerates the exact fields surfaced: usage, daily limit, plan name, upgrade options. The vague tool name 'quota' is fully disambiguated. It doesn't need sibling differentiation because none of the listed siblings (query_sql, analyze_table, etc.) are quota-related.

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?

Usage is only implied — an agent can infer 'call this when you need to know your plan or remaining quota' but the description never states the trigger, prerequisites, or when another tool would be preferable. For a no-param self-evident tool this is acceptable but thin.

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

All ThinAir Data 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?