Retrieve a Braze dashboard user account by SCIM ID to verify identity, audit access, or sync provisioning data.
Get a dashboard user account by SCIM ID.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | Braze REST API key (requires SCIM permissions) | |
| user_id | Yes | SCIM user ID | |
| restEndpoint | No | Braze REST endpoint URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, but 'Get' clearly implies a read-only, non-destructive operation. It does not disclose auth requirements, rate limits, or error behavior, leaving only the minimum behavioral signal.
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 no wasted words. The verb, resource, and lookup key are all present immediately.
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 read tool with fully described parameters, this is almost enough to call correctly. It could be more complete by routing from scim_users_search or noting SCIM permissions, but the core operation is clear.
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%, and the description mirrors the user_id semantics with 'SCIM ID'. It adds no syntax or format beyond what the schema already documents, so baseline 3 is appropriate.
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 ('Get'), resource ('dashboard user account'), and lookup key ('SCIM ID'). This distinguishes it from scim_users_search, which would not fetch by ID.
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 SCIM ID' implies usage when a SCIM ID is known, but there is no explicit when-not guidance or named alternative such as scim_users_search. Usage is inferable but not fully directed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.