ThinAir Data

issue_api_key

Issue a fresh ta_data_* API key for ThinAir DATA (databases/SQL) for your current tenant, and rotate: any previous key keeps working for one hour, then stops — the response reports how many and exactly when (previous_keys_retiring, previous_keys_retire_at). Use it to rotate, or when an integration needs a key and can't reach the console. The new key is tied to your existing plan tier. Rate-limited to 5 issuances per tenant per day. NOTE: this key works ONLY against ThinAir Data — it does NOT authenticate against ThinAir Geo, which issues its own ta_geo_* key from its own identically-named tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`plan`	No
`user`	No
`error`	No
`usage`	No
`key_id`	No	Non-secret fingerprint of the issued key. Safe to log and surface in UI.
`status`	Yes
`api_key`	No	One-time API key secret. Returned only on successful creation, in both structuredContent.api_key and content[0].text — save it immediately. The server stores only sha-256 of the secret; once this response is lost, the key is unrecoverable and must be rotated. Matches AWS IAM / Stripe / GitHub PAT one-time-reveal semantics.
`tenantId`	No
`retry_after_s`	No
`previous_keys_retiring`	No	How many previously-live keys this mint scheduled to retire. issue_api_key rotates: after the grace window the returned key is the only live key on the tenant. 0 means there was nothing else.
`previous_keys_retire_at`	No	ISO 8601 instant when the previous keys stop working (one hour after this mint). Present only when previous_keys_retiring > 0. Update anything still using them before this time.
`credential_returned_once`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

addedOutput schema / properties / previous_keys_retire_at

Added value: +{
+  "description": "ISO 8601 instant when the previous keys stop working (one hour after this mint). Present only when previous_keys_retiring > 0. Update anything still using them before this time.",
+  "type": "string"
+}

addedOutput schema / properties / previous_keys_retiring

Added value: +{
+  "description": "How many previously-live keys this mint scheduled to retire. issue_api_key rotates: after the grace window the returned key is the only live key on the tenant. 0 means there was nothing else.",
+  "minimum": 0,
+  "type": "integer"
+}

removedOutput schema / properties / revoked_previous

Removed value: -{
-  "description": "How many previously-live keys this mint revoked. issue_api_key rotates: the returned key is the only live key on the tenant. 0 means there was nothing else to revoke.",
-  "minimum": 0,
-  "type": "integer"
-}

Changed1 schema field changedSep 3, 2026

addedOutput schema / properties / revoked_previous

Added value: +{
+  "description": "How many previously-live keys this mint revoked. issue_api_key rotates: the returned key is the only live key on the tenant. 0 means there was nothing else to revoke.",
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedMay 1, 2026

changedOutput schema / properties / api_key / description

Previous value: -"One-time API key secret. Returned only on successful creation. Treat as a credential — never log, echo, or render in text channels."New value: +"One-time API key secret. Returned only on successful creation, in both structuredContent.api_key and content[0].text — save it immediately. The server stores only sha-256 of the secret; once this response is lost, the key is unrecoverable and must be rotated. Matches AWS IAM / Stripe / GitHub PAT one-time-reveal semantics."

Changed1 schema field changedMay 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "api_key": {
+      "description": "One-time API key secret. Returned only on successful creation. Treat as a credential — never log, echo, or render in text channels.",
+      "type": "string"
+    },
+    "credential_returned_once": {
+      "type": "boolean"
+    },
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "key_id": {
+      "description": "Non-secret fingerprint of the issued key. Safe to log and surface in UI.",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "plan": {
+      "type": "string"
+    },
+    "retry_after_s": {
+      "type": "number"
+    },
+    "status": {
+      "enum": [
+        "success",
+        "error"
+      ],
+      "type": "string"
+    },
+    "tenantId": {
+      "type": "string"
+    },
+    "usage": {
+      "type": "string"
+    },
+    "user": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedApr 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations, the description discloses rotation semantics (previous key works for one hour), response fields (previous_keys_retiring, previous_keys_retire_at), plan-tier binding, a daily rate limit, and auth scope. No contradictions with annotations; the behavioral detail is rich and actionable.

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?

Every sentence adds operational value: action, rotation, response, use case, rate limit, and scope exclusion. The description front-loads the core action and then layers necessary constraints without fluff.

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

Completeness5/5

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

With no parameters and an output schema present, the description covers all behavioral context an agent needs: rotation timing, rate limit, scope, and use cases. There are no significant gaps for selecting or invoking this tool.

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 zero parameters and schema coverage is 100%, so the description is not required to explain inputs. It still adds relevant contextual scoping ('current tenant') and key-format behavior, earning the baseline for a no-param tool.

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 action ('issue'), the resource (ta_data_* API key), target (ThinAir DATA/SQL, current tenant), and distinguishes it from a Geo sibling key. Clear enough for an agent to identify this as the key-issuance tool among the sibling data tools.

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?

Explicitly says 'Use it to rotate, or when an integration needs a key and can't reach the console.' Also provides a when-not and an alternative: the key does not authenticate against ThinAir Geo, which has its own tool issuing ta_geo_*.

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?