Cromanion

cromanion_config

Read-only

Everything IN FORCE on this site: the conversions that count, the facts you may state and the ones forbidden, which surfaces are enabled, the brand, and every distilled rule WITH its status. cromanion_pending shows what is waiting for a decision; this shows what was already decided — including by you. Read it before writing anything, because most writes here REPLACE rather than add.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`hint`	No
`brand`	No
`goals`	Yes	Conversions that COUNT. `source` says who defined each — `agent` is one of yours.
`voice`	Yes	The client's raw text plus the COMPILED buckets: `tone` steers the prompt, `assertions` are facts somebody vouches for, `interdicts` are enforced in code after the model has spoken.
`domains`	Yes
`surfaces`	Yes	Enabled surfaces, the modal switch, stored CSS, and which surfaces carry custom markup.
`editGenres`	Yes
`youMayDecide`	No
`observedPaths`	No
`playbookRules`	Yes	Distilled rules in EVERY state — `proposed`, `approved`, `paused`, `rejected`. This is how you find a rule you paused in order to un-pause it.
`excludedVisitors`	No	Present only with the measurement permission. ABSENT means you may not see it — not that nobody is excluded.

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"
+}

AddedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds valuable context: this tool reflects already-decided state, including the caller's own decisions, and warns that writes on the site replace rather than add. This goes beyond the annotation without contradicting it.

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?

Three front-loaded sentences deliver the core purpose, a category list, the sibling alternative, and a usage warning. The enumeration is slightly dense but each sentence earns its place; no filler or repetition of schema content.

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 read-only tool with one optional parameter and an output schema, the description fully covers purpose, scope, sibling relationship, and when to invoke it. Nothing an agent needs to call it correctly 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?

Schema description coverage is 100%, and the siteId parameter is already thoroughly documented, even cross-referencing cromanion_grants and explaining the refusal behavior when omitted. The free-text description adds no parameter-specific meaning, so the baseline of 3 applies.

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 clear read purpose — showing everything 'in force' on a site — and enumerates the content categories (conversions, allowed/forbidden facts, surfaces, brand, rule statuses). It explicitly distinguishes itself from cromanion_pending, which shows undecided items, so an agent can tell this tool apart from its siblings.

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?

It gives an explicit when-to-use rule ('Read it before writing anything') and names the alternative for pending decisions (cromanion_pending). The warning that most writes replace rather than add reinforces why consulting this tool first matters, leaving no ambiguity about its role.

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?