Cromanion

cromanion_verify_claim

Idempotent

Redeem a claim once you have published one of its three proofs (a /.well-known file, a tag, or a DNS TXT record). On success it creates the account and the site and returns the tracking snippet to install. Idempotent — safe to retry. Requires the claim secret as a bearer token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`site`	Yes
`status`	Yes	`created` the first time, `existing` on a retry — the same account either way.
`install`	Yes
`provedBy`	No	Which of the three proofs we actually read.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "install": {
+      "properties": {
+        "docs": {
+          "type": "string"
+        },
+        "publicKey": {
+          "type": "string"
+        },
+        "snippet": {
+          "description": "Paste this before </body> on every page. Do not assemble your own.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "publicKey",
+        "snippet"
+      ],
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "provedBy": {
+      "description": "Which of the three proofs we actually read.",
+      "enum": [
+        "well_known",
+        "meta_tag",
+        "dns_txt",
+        "account_holder"
+      ],
+      "type": "string"
+    },
+    "site": {
+      "properties": {
+        "domain": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "mode": {
+          "description": "Always `learn` for a new site.",
+          "enum": [
+            "learn",
+            "act"
+          ],
+          "type": "string"
+        },
+        "plan": {
+          "description": "Always `free` for a new account.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "domain",
+        "mode"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "description": "`created` the first time, `existing` on a retry — the same account either way.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "status",
+    "site",
+    "install"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already cover idempotency and non-read-only behavior; the description adds valuable context by specifying that the claim secret must be a bearer token and that success creates the account/site and returns a tracking snippet. It does not contradict the annotations and provides meaningful side-effect and auth information.

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 description is concise, well-structured, and front-loaded with the core action. Every sentence earns its place: the precondition, the success outcome, and the idempotency/auth requirement.

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?

For a tool with an empty input schema and an output schema available, the description covers all essential operational context: prerequisites, proof types, auth mechanism, retry safety, and success behavior. Nothing critical 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?

With zero parameters, the schema leaves nothing to document, and the baseline is 4. The description still adds relevant input-related context by requiring the claim secret as a bearer token, which is essential for correct invocation.

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 description clearly states the specific action ('redeem a claim') and the precondition ('once you have published one of its three proofs'), which distinguishes it from earlier claim-lifecycle siblings like open_claim or claim_domain. It also names the concrete outcomes: creating the account and site and returning a tracking snippet.

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?

The description gives clear context for when to use it: after publishing a /.well-known file, meta tag, or DNS TXT record. It does not explicitly name sibling alternatives or state when not to use it, so it stops short of full exclusions.

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

All Cromanion tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?