GetBanksGet a list of all banks available on RozbijBank platform. Returns bank titles (use these exact names as bankName filter in SearchPersonalAccounts, SearchSavingsAccounts, SearchDeposits, SearchBusinessAccounts, and SearchPromotions). The bankName filter uses substring matching, so partial names work too.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is safe, read-only, and idempotent. The description adds that it returns bank titles intended as filter values, which is useful context beyond the annotations. However, it does not describe output structure or pagination.
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?
Three sentences, no waste. The first sentence identifies the purpose, the second gives usage guidance, and the third clarifies matching behavior.
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?
Given no parameters and no output schema, the description covers the tool's purpose and output usage completely. It also references sibling tools, giving contextual completeness.
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 has zero parameters, so there is nothing to explain. The description adds no parameter details because none exist, which 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?
The description clearly states the tool gets a list of all banks, using a specific verb and resource. It differentiates itself from sibling search tools by positioning itself as the source of bank names for filters.
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?
It explicitly tells agents to use the returned bank titles as bankName filter in specific sibling tools, and explains substring matching behavior. This gives clear direction on when to call this tool before searches.
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.