Skip to main content
Glama

Cromanion

by com.cromanion
OverviewDiscussionsAdmin

cromanion_decide

Idempotent

Rule on one thing from cromanion_pending: pass its kind and id back unchanged with a decision. approve / reject for everything; pause additionally for a playbook rule. Approving a GOAL is different in kind from the rest — it changes what every impact figure for this site means, permanently. You cannot edit rule text here, only rule on it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe item's id, exactly as cromanion_pending returned it. Ids are not shared across kinds.
allNoRule on every discovered page at once, ignoring `id`. observed_path only — the other kinds are decided one at a time, as in the console.
kindYesWhich queue the item came from. Copy it back from cromanion_pending unchanged.
siteIdNoWhich 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.
decisionYesA status and nothing else — rule TEXT is edited by cromanion_set_playbook. `pause` applies only to a playbook_rule.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
okYes
kindYes
ruledNoPresent with `all`: how many were ruled on. Zero is a success — there was nothing waiting.
summaryNoWhat the ruling changed, in one line you can repeat to your human.
decisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / all
      Added value: +{
+  "description": "Rule on every discovered page at once, ignoring `id`. observed_path only — the other kinds are decided one at a time, as in the console.",
+  "type": "boolean"
+}
    • changedInput schema / properties / decision / description
      Previous value: -"A status and nothing else — there is no way to edit an item's text here. `pause` applies only to a playbook_rule."New value: +"A status and nothing else — rule TEXT is edited by cromanion_set_playbook. `pause` applies only to a playbook_rule."
    • changedInput schema / required
      Previous value: -[
-  "kind",
-  "id",
-  "decision"
-]New value: +[
+  "kind",
+  "decision"
+]
    • addedOutput schema / properties / ruled
      Added value: +{
+  "description": "Present with `all`: how many were ruled on. Zero is a success — there was nothing waiting.",
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "ok",
-  "kind",
-  "id",
-  "decision"
-]New value: +[
+  "ok",
+  "kind",
+  "decision"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "decision": {
+      "enum": [
+        "approve",
+        "reject",
+        "pause"
+      ],
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "edit_genre",
+        "playbook_rule",
+        "goal",
+        "observed_path"
+      ],
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "summary": {
+      "description": "What the ruling changed, in one line you can repeat to your human.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "kind",
+    "id",
+    "decision"
+  ],
+  "type": "object"
+}
  4. Changed3 schema fields changed
    • addedInput schema / properties / decision / description
      Added value: +"A status and nothing else — there is no way to edit an item's text here. `pause` applies only to a playbook_rule."
    • addedInput schema / properties / id / description
      Added value: +"The item's id, exactly as cromanion_pending returned it. Ids are not shared across kinds."
    • addedInput schema / properties / kind / description
      Added value: +"Which queue the item came from. Copy it back from cromanion_pending unchanged."
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses the consequential, permanent semantic effect of approving a GOAL — that it changes what every impact figure for this site means. Also clarifies that the decision is a status only, not editable rule text, adding real behavioral context beyond the annotations.

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?

Four dense, purposeful sentences with the core instruction front-loaded. Each sentence earns its place: what to pass, which decisions apply to what, the critical GOAL caveat, and the edit limitation. No filler or repetition.

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?

Completeness is achieved given the output schema and rich parameter descriptions. The description covers the call pattern, decision applicability, the most important semantic consequence, and the boundary with sibling tools, so an agent has enough to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by warning that approving a GOAL permanently changes impact figures and by emphasizing that kind and id must be passed back unchanged. This is useful but not required for every parameter.

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 action — 'Rule on one thing from cromanion_pending' — and enumerates the exact decision values. It also distinguishes itself from rule-text editing by saying 'You cannot edit rule text here, only rule on it,' which separates it from cromanion_set_playbook.

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?

Provides clear scope: approve/reject apply to everything, pause applies only to playbook_rule, and rule text must not be edited here. It implies the alternative (edit via cromanion_set_playbook) through the negative constraint but does not explicitly name it in the description.

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

All Cromanion toolsInspect
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