Retrieve all Brivo administrator roles to review permissions and assign access correctly. Use this read-only query to inspect role definitions without making changes.
List all Brivo administrator roles.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The word 'all' implies no filtering or pagination, which is a small useful signal, but nothing is said about result size, ordering, or whether roles are scoped to an account.
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?
A single front-loaded sentence with zero waste. Nothing is padded or restated from the name.
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 no-param list tool with no output schema, the description is minimally adequate, but it never clarifies the relationship to List_administrator_roles or describes the shape of a returned role. There is no output schema to offload that responsibility to.
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?
Zero parameters, so per the rubric the baseline is 4. The description correctly implies no filtering inputs exist, consistent with the empty schema.
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?
States a clear verb+resource ('List all Brivo administrator roles'), so the operation is unambiguous. It does not, however, differentiate itself from the sibling List_administrator_roles, which an agent could easily confuse it with.
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?
There is no guidance on when to use this tool versus List_administrator_roles, Get_admin_assignments, or any of the other role/permission-adjacent siblings. The agent is left to guess at the boundary between 'roles' and 'administrator roles'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.