Retrieve a single Brivo administrator by ID to inspect their account details and permissions.
Retrieve a single Brivo administrator by id.
| Name | Required | Description | Default |
|---|---|---|---|
| administratorId | Yes | The Brivo administrator id, e.g. from Administrator: List_administrators. |
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. The description adds no behavioral context beyond that: no auth/permission requirements, no behavior for an unknown id, no indication of what the response contains. With the annotation bar lower, it still contributes nothing new.
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 efficient sentence with the verb and resource front-loaded and no filler. Nothing could be trimmed without losing meaning.
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 one-parameter getter with read-only annotations, this is close to adequate, but with no output schema the description does not indicate what a returned administrator looks like or what happens when the id is unknown. Minor gaps remain for an agent to call it confidently.
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 description coverage is 100% and the single parameter is fully documented in the schema, including where to obtain the id. The description's 'by id' restates rather than extends the schema, 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 and resource: retrieve a single Brivo administrator identified by id. It is clearly a getter, but it does not distinguish itself from close siblings such as Get_current_administrator or Get_administrator_login, 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?
The phrase 'by id' implies you must already have an identifier, but there is no explicit when-to-use guidance and no mention of when to prefer Get_current_administrator or Get_administrator_login instead. The schema's reference to 'Administrator: List_administrators' is the only routing hint, and it lives in the schema rather than the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.