Atly

Show my key and quota

get_api_key

Read-only

Show my key, tier and remaining quota

Who am I and how much quota is left. Works without a key too (then it describes the anonymous allowance for your IP).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tier`	No
`label`	No
`quota`	No
`key_id`	No
`call_id`	No
`doc_notes`	No
`email_verified`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / quota / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "anyOf": [
-          {
-            "description": "Calls allowed per window.",
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Calls allowed per window."
-      },
-      "remaining": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "resets_at": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "window": {
-        "anyOf": [
-          {
-            "enum": [
-              "hour",
-              "day"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "limit": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Calls allowed per window."
+      },
+      "remaining": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "resets_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "window": {
+        "anyOf": [
+          {
+            "enum": [
+              "hour",
+              "day"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false. The description adds genuinely new behavioral context beyond them: the tool is callable unauthenticated and degrades to IP-based anonymous allowance, which an agent could not infer from the annotations.

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?

Two short sentences, front-loaded with what is returned. The second sentence partly restates the first ('Who am I and how much quota is left' echoes 'my key, tier and remaining quota'), which is minor redundancy rather than bloat.

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?

With an output schema present, the description needn't explain return structure, and with zero parameters there's nothing else to cover. The unauthenticated case is covered; the only light gap is not stating whether the key is redacted or returned in full, but that is arguably output-schema territory.

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?

The tool takes zero parameters, so the baseline is 4; there are no parameter semantics for the description to compensate for.

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 set — key, tier and remaining quota — plus the anonymous-allowance behavior, so an agent knows exactly what it returns. Differentiation from siblings is trivial since none of them touch credentials, but the description doesn't say so explicitly, keeping it just shy of a 5.

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 clear context for both invocation modes: call it to answer 'who am I and how much quota is left,' and it still works without a key, in which case it returns the anonymous allowance for your IP. No alternatives or exclusions are named, but the sibling tools are unrelated, so there's little to route against.

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

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