Boardroom Revenue Control

Who am I (token and workspace)

whoami

Read-onlyIdempotent

Who this token is, which workspace it can read, and which scopes it carries. Call this first: it tells you which of the other tools will work.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ok`	No	False when the call was refused or failed; see error.
`error`	No	Machine-readable refusal code (a string), present only when ok is false.
`message`	No	Human-readable explanation of a refusal (a string).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "error": {
+      "description": "Machine-readable refusal code (a string), present only when ok is false."
+    },
+    "message": {
+      "description": "Human-readable explanation of a refusal (a string)."
+    },
+    "ok": {
+      "description": "False when the call was refused or failed; see error.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedOct 9, 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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the non-obvious behavioral trait that this call gates the usefulness of the other tools, which the annotations cannot express. It does not discuss auth requirements or error behavior when a token is invalid, keeping it out of the top band.

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?

Two tight sentences, zero filler, and the identity/scope payload is front-loaded ahead of the call-ordering advice. Every clause earns its place.

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?

An output schema exists, so the return shape is covered elsewhere; with no parameters and no nested objects, the only thing an agent needs is what it reveals and when to call it, both of which are stated.

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?

The tool takes no parameters, so the baseline is 4. There is nothing further the description could add about inputs.

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 precisely what is returned — token identity, readable workspace, and carried scopes — with a specific resource (the auth token) rather than a generic 'get info'. An agent can distinguish this diagnostic from every sibling tool (crm_*, marketing_*, agent_*) without opening the schema.

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?

'Call this first' gives an explicit ordering instruction and a reason (it tells you which other tools will work), which is unusually actionable guidance. It stops short of naming specific alternatives or exclusions, but for a zero-parameter prerequisite tool that omission is minor.

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

All Boardroom Revenue Control tools Inspect

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.