action1-mcp-server

Get enterprise license information

action1_get_subscription

Read-onlyIdempotent

Retrieves enterprise license details to verify subscription status and manage enterprise permissions.

Instructions

Get enterprise license information. Gets details about the enterprise license. Perm: manage_enterprise.

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
`id`	No
`MSP`	No
`self`	No
`type`	No
`exceeded`	No
`license_type`	No
`license_status`	No
`license_expires`	No
`free_endpoint_count`	No
`actual_endpoint_count`	No
`licensed_endpoint_count`	No
`endpoint_count_coefficient`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 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 / MSP
```
Added value: +{}
```
- addedOutput schema / properties / actual_endpoint_count
```
Added value: +{}
```
- addedOutput schema / properties / endpoint_count_coefficient
```
Added value: +{}
```
- addedOutput schema / properties / exceeded
```
Added value: +{}
```
- addedOutput schema / properties / free_endpoint_count
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / license_expires
```
Added value: +{}
```
- addedOutput schema / properties / license_status
```
Added value: +{}
```
- addedOutput schema / properties / license_type
```
Added value: +{}
```
- addedOutput schema / properties / licensed_endpoint_count
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

C2.8/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 elsewhere. The description adds one genuinely non-structured fact — the required permission 'manage_enterprise' — but says nothing about what the license payload contains or whether scope is org- or enterprise-wide.

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?

Very short, but it wastes roughly half its length on a redundant restatement of the title. The permission note is useful; the middle sentence is filler.

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 carry behaviour; the permission note covers auth. However, for a tool sitting among many licence/subscription lookups, the omission of any disambiguation leaves a real selection gap.

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% with only two optional params (verbose, response_format), so the schema fully documents them. The description adds no guidance on the non-obvious 'verbose' flag ('Skip per-item compactor'), which would have been valuable, so it does no better than the baseline.

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

Purpose3/5

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

It does state a verb and resource ('Get enterprise license information'), but the second sentence ('Gets details about the enterprise license') is a near-tautological restatement that adds nothing. Critically, it never distinguishes this from close siblings like action1_get_enterprise or action1_get_subscription_usage, so the agent must guess which licence-related tool to pick.

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 or when-not-to-use guidance, and no mention of alternatives despite several subscription/licence siblings. The only usable signal is the 'Perm: manage_enterprise' requirement, which is a prerequisite rather than selection guidance.

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

Deploy Server