action1-mcp-server

Get usage statistics for organizations

action1_list_subscription_usage_organizations

Read-onlyIdempotent

Retrieve per-organization license usage statistics to monitor subscription consumption and manage allocations.

Instructions

Get usage statistics for organizations. Gets details about license usage with statistics for each organization individually. Perm: manage_organizations.

Input Schema

Name	Required	Description	Default
`verbose`	No	Skip per-item compactor.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

addedOutput schema / properties / items / items / properties

Added value: +{
+  "current_active_endpoint_count": {},
+  "current_inactive_endpoint_count": {},
+  "id": {},
+  "monthly_average_endpoint_count": {},
+  "organization": {},
+  "self": {},
+  "type": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds the required permission (manage_organizations), which is genuine context beyond the schema, but says nothing about whether results span all organizations, whether there is pagination, or how large the response can be.

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 short sentences, front-loaded with the purpose. The middle sentence largely restates the first ('Gets details about license usage ... for each organization individually'), which is mild redundancy but not harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only, zero-required-parameter tool with a full output schema, the definition covers purpose, scope and the permission gate, which is close to sufficient. The remaining gap is disambiguation from the sibling subscription-usage tools, which is only implied by 'each organization individually'.

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 coverage is 100% for both optional parameters ('verbose' and 'response_format' with its enum), so the schema carries the parameter burden. The description mentions no parameters at all and adds no meaning about when verbose mode matters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get usage statistics for organizations') and adds scope ('statistics for each organization individually'), which makes it distinguishable from a single-org read. It never names the close siblings action1_get_subscription_usage or action1_get_org_subscription_usage, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Perm: manage_organizations', which is a prerequisite rather than a when-to-use rule. With three overlapping subscription-usage tools in the sibling list, an agent gets no instruction about which one to pick or when this one is the wrong choice.

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

Deploy Server