canli-validation-mcp

Get a free validation key

get_key

Issue a free validation key for a session. Rarely needed because the first validation request issues one automatically unless a key is set or local mode is used.

Instructions

Issue a free validation key for this session. Rarely needed: the first validation issues one itself unless CANLI_KEY or local mode is set, and the read tools need none. Quotas: 1000 validations per key per UTC day, 5 keys per client per UTC day, 1048576 bytes per validation request, 1024 bytes per key revocation request, 20000 observations per series, 200 variants per matrix.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`label`	No	Name for the key.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`note`	No
`error`	No
`key_source`	No
`key_present`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.13.0Oct 7, 2026

removedOutput schema / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / data / additionalProperties
```
Removed value: -{}
```

changedOutput schema / properties / error / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedv0.10.1Sep 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 / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "description": "key_source says which key the session uses; data.key is set when a new key was issued.",
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "error": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "key_present": {
+      "type": "boolean"
+    },
+    "key_source": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.6.0Sep 26, 2026
- addedInput schema / properties / label / description
```
Added value: +"Name for the key."
```
First observedv0.5.0Sep 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description goes well beyond them by disclosing concrete quotas: 1000 validations/key/UTC day, 5 keys/client/UTC day, per-request byte limits, and series/matrix size caps. It also discloses the auto-issuance behavior of the first validation call, which is genuine operational context.

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?

Front-loaded with the core purpose, then the rarely-needed caveat, then quotas. The quota sentence is a dense run-on list, but every figure is actionable operational data rather than filler, so it earns its place.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, necessity, prerequisites, and rate limits. Nothing an agent needs to decide whether and how to call this tool is missing.

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?

There is only one optional parameter ('label'), and schema description coverage is 100%, so the schema already documents it fully. The description adds no semantics for the label beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

The first sentence gives a specific verb+resource ('Issue a free validation key for this session'). It also differentiates itself from the sibling validate_* tools by stating that read tools need no key, so an agent can route correctly without opening a schema.

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 states when this tool is NOT needed ('Rarely needed: the first validation issues one itself unless CANLI_KEY or local mode is set, and the read tools need none'), which is exactly the when/when-not guidance required. It names the conditions (CANLI_KEY set, local mode) that make the call unnecessary.

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