Tracklution

Show API key info

get_api_key_info

Read-only

API key inspection only — does NOT return any analytics data. Shows the key name, prefix, how many containers it can access, and when it expires, for every connected server.

USE WHEN:

The user asks "which account / key am I connected with?" or "when does my key expire?".
You hit an authorization error and need to confirm the key is still valid.

For any data question, skip this and go straight to get_summary or get_report.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`servers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedOutput schema / properties / servers / items / properties / key / properties / dashboard_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed3 schema fields changedOct 20, 2026

changedOutput schema / properties / servers / items / properties / key / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / servers / items / properties / key / properties / clients

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "pii_redacted": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "id",
+      "pii_redacted"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / servers / items / properties / key / properties / pii_redacted
```
Added value: +{
+  "type": "boolean"
+}
```

First observedSep 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover readOnly/non-destructive, and the description adds value beyond them: it clarifies the output is diagnostic metadata, not analytics, and discloses that results span every connected server (a non-obvious multi-server behavior). It doesn't mention failure modes (e.g., what happens with an invalid/expired key), so it sits just under full marks.

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?

The negation-and-scope line is front-loaded, the returned fields come next, and the routing/exclusions come last. Every clause carries decision-relevant information; there is no filler.

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 an output schema present, the description needn't document return structure, yet it still names the four key fields. For a zero-param read tool with annotations, nothing an agent needs in order to select and 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, so the baseline is 4. The description implicitly confirms a no-argument call ('for every connected server') and doesn't introduce any confusing parameter-like language.

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 and resource ('API key inspection') and immediately negates the most likely misread ('does NOT return any analytics data'). Explicitly enumerates returned fields (key name, prefix, container count, expiry) and the 'every connected server' scope, which separates it cleanly from get_summary/get_report.

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?

A dedicated USE WHEN block gives two concrete triggers (identity/expiry questions, authorization errors) and an explicit exclusion with a named alternative: 'For any data question, skip this and go straight to get_summary or get_report.' This is the strongest form of routing guidance.

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

All Tracklution 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?