Tokenrip

Show actions usage

actions_usage

Read-onlyIdempotent

Read this month's actions for your account, or a team you belong to (team): the plan, the actions used and the limit (null: no limit), when the allowance resets (resetsAt, the 1st of the next month, UTC), mode (measure: nothing is paused; enforce: agents' changes are paused at the limit), and the actions per workspace, each with its agents (each a principal by handle, the busiest first, with its count) and unattributed (actions no agent is recorded for: before per-agent counting began, or a platform admin's removal). A workspace in the trash still lists its count; workspaces purged for good read as one entry with null id, slug and name. An action is one agent operation that changed a workspace and shows in its history: a bulk change counts once per workspace it changes; reads, failed attempts, a person's own changes in the browser and work outside a workspace are free. A workspace's actions count toward its owner, whoever's agent made them. A platform admin reads any team, or another account with account (an account id or alias; anyone else: FORBIDDEN).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "actions_usage"
  }
}

Input Schema

Name	Required	Description	Default
`team`	No	A team's actions, by slug or id (members only; a platform admin reads any team's).
`account`	No	Another account's actions, by account id or alias (platform admins only; anyone else is refused FORBIDDEN). Not with team.

Output Schema

Name	Required	Description	Default
`mode`	Yes
`plan`	Yes
`used`	Yes
`limit`	Yes
`payer`	Yes
`resetsAt`	Yes
`workspaces`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026

addedOutput schema / properties / workspaces / items / properties / agents

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "actions": {
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "agent": {
+        "additionalProperties": false,
+        "properties": {
+          "account": {
+            "additionalProperties": false,
+            "properties": {
+              "alias": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "former": {
+                "const": true,
+                "type": "boolean"
+              },
+              "id": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "alias"
+            ],
+            "type": "object"
+          },
+          "agent": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "harness": {
+                    "anyOf": [
+                      {
+                        "type": "string"
+                      },
+                      {
+                        "type": "null"
+                      }
+                    ]
+                  },
+                  "id": {
+                    "anyOf": [
+                      {
+                        "format": "uuid",
+                        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+                        "type": "string"
+                      },
+                      {
+                        "type": "null"
+                      }
+                    ]
+                  },
+                  "name": {
+                    "anyOf": [
+                      {
+                        "type": "string"
+                      },
+                      {
+                        "type": "null"
+                      }
+                    ]
+                  }
+                },
+                "required": [
+                  "id",
+                  "name",
+                  "harness"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "isCaller": {
+            "type": "boolean"
+          },
+          "mine": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "account",
+          "agent",
+          "mine",
+          "isCaller"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "agent",
+      "actions"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / workspaces / items / properties / unattributed

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / workspaces / items / required

Previous value: -[
-  "id",
-  "slug",
-  "name",
-  "actions"
-]New value: +[
+  "id",
+  "slug",
+  "name",
+  "actions",
+  "agents",
+  "unattributed"
+]

AddedOct 31, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare a safe read, and the description adds substantial context beyond them: reset timing (1st of next month, UTC), mode semantics (measure vs enforce pausing agents), trash vs purged workspace representation (null id/slug/name), what counts as billable (bulk changes per workspace; reads and browser edits free), and owner attribution. This is unusually rich behavioral disclosure for a reporting tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, but the single dense paragraph packs long parentheticals (mode, unattributed, purged workspaces) that make it hard to scan. Nearly every clause carries real information, yet it would benefit from being split into purpose / semantics / permissions sections.

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 an output schema present, the description needn't explain return shape, and it still covers both optional parameters, permission edge cases, reset timing, enforcement mode, and attribution rules. Nothing material 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: team is limited to membership unless platform admin, and account is admin-only and incompatible with team. Most of this overlaps the schema descriptions, with modest added nuance about "a team you belong to."

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 opening clause gives a specific verb and resource plus scope: "Read this month's actions for your account, or a team you belong to." It further defines what an action is (an agent operation that changed a workspace), which cleanly separates it from sibling tools like storage_usage, activity, or connection_audit_recent.

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 states the argument conditions clearly: use team for a team you belong to, account for another account, and these are mutually exclusive ("Not with team" in the schema). Permission outcomes are explicit (FORBIDDEN for non-admins). It does not name an alternative sibling tool for related usage questions, which keeps it just short of a 5.

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

All Tokenrip 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.