List MSP360 licenses to track allocation. Filter to unassigned licenses to identify available capacity.
List available MSP360 licenses, optionally filtered to only unassigned ones.
| Name | Required | Description | Default |
|---|---|---|---|
| isAvailable | No | Only return unassigned licenses. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It discloses the optional unassigned filter and implies a read-only listing, but doesn't mention response shape, pagination, or any limitations. Acceptable for a simple list tool, but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence with no filler; the core action and the optional parameter are both front-loaded. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one optional parameter and no output schema, the description supplies the essential invocation information. It is slightly light on what 'available' means and what the response contains, but it remains adequate for correct use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%: the isAvailable parameter is already documented as 'Only return unassigned licenses.' The description restates this filter but adds no new semantic detail, so the baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb ('List') and resource ('MSP360 licenses') and mentions the optional unassigned filter. It doesn't explicitly contrast with msp360_get_license, but the plural 'licenses' and list intent make the distinction obvious enough.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to choose this tool over siblings like msp360_get_license, nor any exclusions. The usage is only implied by the name and description, not explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.