Retrieve a single Brivo access group by ID to inspect its details, enabling read-only access-control review without modifying account data.
Retrieve a single Brivo access group by id.
| Name | Required | Description | Default |
|---|---|---|---|
| groupId | Yes | The Brivo group id, e.g. from Group: List_groups. |
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 elsewhere. The description adds no behavioral context beyond 'Retrieve' — nothing on what is returned, error behavior for an invalid id, or authorization needs.
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 filler or redundancy. 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 id-based read, annotations cover safety and the schema covers the sole parameter, so the core is adequate. However, with no output schema and no statement of what is returned, the definition is only minimally complete.
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?
With a single parameter at 100% schema coverage, the schema fully documents groupId, including its origin from List_groups. The description only echoes 'by id' and adds no format or constraint detail, so the baseline 3 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?
States a specific verb (Retrieve) and resource (Brivo access group), scoped to a single item by id, which implicitly separates it from the plural List_groups sibling. It stops short of explicitly naming the alternative, so differentiation relies on the agent noticing 'single' vs the sibling's 'List'.
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 when-to-use guidance or alternatives are stated. The only routing hint ('e.g. from Group: List_groups') lives in the schema's groupId description, not in the tool description, so the description itself offers no usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.