action1-mcp-server

Get usage statistics for a specific organization

action1_get_org_subscription_usage

Read-onlyIdempotent

Retrieve license usage statistics for a specific organization by its ID to monitor subscription consumption and manage organization licensing.

Instructions

Get usage statistics for a specific organization. Gets details about license usage for an organization specified by its ID. Perm: manage_organizations.

Input Schema

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

Output Schema

Name	Required	Description	Default
`id`	No
`self`	No
`type`	No
`organization`	No
`current_active_endpoint_count`	No
`monthly_average_endpoint_count`	No
`current_inactive_endpoint_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 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 / current_active_endpoint_count
```
Added value: +{}
```
- addedOutput schema / properties / current_inactive_endpoint_count
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / monthly_average_endpoint_count
```
Added value: +{}
```
- addedOutput schema / properties / organization
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description's one genuine addition is the permission requirement ("Perm: manage_organizations"), which is real auth context. It says nothing about result shape, pagination, or scoping, so it is modest value on top of annotations rather than rich disclosure.

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?

Two short sentences, but the second largely restates the first ("Gets details about license usage for an organization specified by its ID") before adding the permission note. The useful content — the perm requirement — is buried at the tail rather than front-loaded.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations plus 100% schema coverage carry much of the burden. The missing piece is disambiguation from the two similar subscription-usage siblings, which is exactly what the description should supply and does not.

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 description coverage is 100%, so the schema documents all three parameters and baseline is 3. The description adds no parameter meaning beyond the schema, and it does not address that org_id is listed as optional (required: []) even though the prose implies an ID is always supplied.

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?

Specific verb+resource ("Get usage statistics for a specific organization") and the second sentence narrows it to license usage keyed by org ID. The gap is sibling differentiation: the tool list contains action1_get_subscription_usage and action1_list_subscription_usage_organizations, and nothing here explains how this one differs.

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?

There is no when-to-use guidance and no exclusions, despite two obviously adjacent usage tools in the sibling list. The only routing signal is the implicit 'per organization' framing, which the agent has to infer.

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

Deploy Server