GetReferralCodeGet a referral/invitation code for a specific bank. Users can use these codes when opening new accounts to get bonuses.
| Name | Required | Description | Default |
|---|---|---|---|
| bankName | Yes | The bank name to get a referral code for (e.g. 'mBank', 'ING') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only and idempotent, so the safety profile is covered. The description adds no extra behavioral details such as return format, caching, or error handling; it only restates the basic function.
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 two concise sentences with the core purpose front-loaded. Every word adds value, and there is no redundant information.
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-only tool with one fully documented parameter, the description is mostly adequate. It could mention what the response contains (the code) and any prerequisites like the bank being supported, but these are largely inferable from the tool name and description.
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 input schema fully covers the single bankName parameter with a description and example, so the schema does the heavy lifting. The tool description does not add additional parameter semantics beyond identifying the bank as the target.
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?
The description clearly states the tool's verb (Get) and resource (referral/invitation code for a specific bank), making its purpose obvious. However, it does not explicitly differentiate from sibling tools like GetBanks or GetPromotionDetails, so it misses the top score.
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 description implies the tool is for fetching a referral code to use when opening a bank account, but it provides no explicit guidance on when to choose this tool over alternatives. The context is present but not clearly framed as a selection criterion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: search tools are clearly separated by product type (accounts, deposits, cards, etc.), and utility tools (calculation, bank list, referral, date) have no overlap. The relationship between SearchPromotions and GetPromotionDetails is a standard search/detail pattern that is easy to understand.
All tools follow a consistent VerbNoun PascalCase pattern (GetBanks, SearchDeposits, CalculateDepositInterest). The verbs Get, Search, and Calculate are used consistently across the set, making the intent of each tool predictable from its name.
With 13 tools, the server is well-scoped for a bank comparison platform. Each tool serves a clear purpose—covering searches for six product types, promotion management, and supporting utilities—without unnecessary bloat or missing essentials.
The tool set covers the full lifecycle of a bank offer comparison workflow: listing banks, searching all major product categories, retrieving promotion details, calculating deposit interest, obtaining referral codes, and accessing educational blog content. No obvious critical gaps are apparent for the stated purpose.