Cromanion

cromanion_grants

Read-only

List what your human has allowed this agent to do, and what they have not. Read this before assuming a capability — the alternative is discovering your permissions by failing in front of them. You cannot change these yourself; only your human can, in their console.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`granted`	Yes	Only what you MAY do. A capability absent from this list is one to stop planning around.
`revoked`	Yes	True once your human has ended this credential. Nothing else will work; do not retry.

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": {
+    "granted": {
+      "description": "Only what you MAY do. A capability absent from this list is one to stop planning around.",
+      "items": {
+        "properties": {
+          "grant": {
+            "description": "The capability token, e.g. `goals`, matching what a refusal names in `neededGrant`.",
+            "type": "string"
+          },
+          "label": {
+            "description": "What your human saw when they allowed it.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "grant"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "revoked": {
+      "description": "True once your human has ended this credential. Nothing else will work; do not retry.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "revoked",
+    "granted"
+  ],
+  "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?

Annotations already declare readOnlyHint and openWorldHint; the description reinforces this by stating 'You cannot change these yourself; only your human can, in their console.' This adds ownership and mutability context beyond the structured fields, though it doesn't describe the output format, which is covered by the output schema.

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 short sentences lead with the core purpose, then a usage warning, then a mutability constraint. No filler; each sentence contributes new information.

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?

With no parameters, a readOnlyHint annotation, and an output schema present, the description covers what the tool lists, when to read it, and how permissions can change. Nothing needed for correct invocation 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?

There are zero parameters and schema coverage is 100%, so the description needs no parameter detail. The baseline for zero-parameter tools is 4.

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 uses a specific verb ('List') and a specific resource ('what your human has allowed this agent to do, and what they have not'), clearly identifying it as a permission introspection tool. This distinguishes it from sibling action tools like cromanion_add_goal and cromanion_decide.

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 explicitly instructs the agent to 'Read this before assuming a capability' and warns that the alternative is 'discovering your permissions by failing in front of them,' which tells when to use it. It doesn't name sibling exclusions, but no sibling offers the same read-only permission list, so the context is sufficient.

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?