Cromanion

cromanion_claim_domain

DestructiveIdempotent

Claim another host for this site so its traffic counts, or give one up with remove: true. A DIFFERENT registrable domain must be proven on its own — publish this claim's challenge there too, then call again. Subdomains need no call at all: a claimed domain already covers them. Needs the site-config permission.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	Yes	A public hostname, e.g. shop.example.com.
`remove`	No	Give the host up instead. Needs no proof — it only narrows what we listen to.
`siteId`	No	Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`note`	No	Present when nothing changed, saying why — usually that a claimed domain already covers this subdomain.
`added`	No	False when the host was already covered — not a failure.
`claimed`	Yes	Every host this site now listens to, after the change. The answer, whichever branch ran.
`removed`	No	Present on a removal: the host given up.
`provedBy`	No	Present when a fresh proof was read, which a different registrable domain requires.

Schema Changelog

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

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / siteId

Added value: +{
+  "description": "Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.",
+  "type": "string"
+}

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "added": {
+      "description": "False when the host was already covered — not a failure.",
+      "type": "boolean"
+    },
+    "claimed": {
+      "description": "Every host this site now listens to, after the change. The answer, whichever branch ran.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Present when nothing changed, saying why — usually that a claimed domain already covers this subdomain.",
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "provedBy": {
+      "description": "Present when a fresh proof was read, which a different registrable domain requires.",
+      "enum": [
+        "well_known",
+        "meta_tag",
+        "dns_txt",
+        "account_holder"
+      ],
+      "type": "string"
+    },
+    "removed": {
+      "description": "Present on a removal: the host given up.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "claimed"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing the site-config permission requirement, the challenge-publication workflow, and the subdomain-coverage behavior. It also reinforces the destructive nature of removal ('give one up') consistent with destructiveHint=true.

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?

Three sentences, front-loaded with the primary action and effect, followed by the key caveat and exclusion. Every sentence earns its place and there is no redundant restating of schema fields.

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 mutation tool with an output schema and fully described parameters, the description covers the critical operational context: permission needed, challenge requirement for new registrable domains, and the subdomain no-op rule. Nothing essential 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?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that the domain must be a different registrable domain and that subdomains are already covered without a call, enriching the meaning of the domain parameter beyond the schema's simple hostname example.

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 states a specific action ('Claim another host for this site so its traffic counts') and the inverse action ('give one up with remove: true'), clearly identifying the resource and effect. It also distinguishes itself from related claim/verification work by noting subdomains need no call, so an agent can tell what this tool is for.

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 when-to-use context ('so its traffic counts'), an explicit when-not-to-use rule ('Subdomains need no call at all'), and the proof workflow for a different registrable domain. It does not name sibling tools like cromanion_verify_claim as alternatives, but the process is concrete enough to guide selection.

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?