Retrieve broker account information by authenticating with the exchange broker master account. Query key account details for management and verification.
Use exchange broker master account to query account information.
Rate limit: 10 req per second.
Rules:
Requires exchange broker master account authentication.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the rate limit and the authentication requirement, which are practical behavioral constraints beyond the annotations. It does not describe response shape or error cases, but that is less critical for a zero-parameter read-only query.
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?
The description is brief and front-loaded with the core purpose, followed by the rate limit and auth rule. There is minor redundancy between 'Use exchange broker master account' and 'Requires exchange broker master account authentication,' but the overall structure is efficient.
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 zero-parameter, read-only account query, the description covers the essentials: what it does, the authentication required, and the rate limit. It does not specify what 'account information' includes or what the response looks like, but the tool name and simplicity make this sufficient.
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?
The tool accepts zero parameters, and the schema is an empty object with 100% coverage. The description correctly emphasizes the only real invocation requirement, broker master account authentication, so no parameter documentation is needed.
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 action ('query') and resource ('broker master account' account information). However, 'account information' is somewhat generic, and there is no explicit differentiation from several sibling account-query tools like getAccountInfo or queryBalance.
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?
Provides clear usage context: this should be called using exchange broker master account authentication, and there is a rate limit of 10 req/s. It does not explicitly mention alternatives or when not to use the tool, but the broker master account requirement gives sufficiently clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.