Skip to main content
Glama

Rozbij Bank - Polish bank offers

by pl.rozbijbank.mcp
OverviewDiscussionsAdmin

Search Bank Promotions

SearchPromotions
Read-onlyIdempotent

Search time-limited bank promotions (promocje) in Poland with tasks, rewards, and deadlines. These are separate from permanent product offers (use Search*Accounts/SearchDeposits for those). Call with no filters to get all active promotions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (starts from 1). Default 1.
sortNoSort by: 'endTime' (default, ending soonest first), 'popularity' (most popular first), 'reward' (highest reward first).endTime
pageSizeNoResults per page (1-20). Default 8.
bankNamesNoFilter by bank names (comma-separated, substring match). Use GetBanks to see all available bank names. Example: 'mBank, ING'. Leave empty to show all banks.
productTypesNoFilter by product type codes (comma-separated). Values: 'personalAccount', 'savingsAccount', 'deposit', 'businessAccount', 'creditCard', 'personalVipAccount'. Leave empty to show all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / bankNames / description
      Previous value: -"Filter by bank names (comma-separated, e.g. 'mBank, ING')"New value: +"Filter by bank names (comma-separated, substring match). Use GetBanks to see all available bank names. Example: 'mBank, ING'. Leave empty to show all banks."
    • changedInput schema / properties / page / description
      Previous value: -"Page number (starts from 1)"New value: +"Page number (starts from 1). Default 1."
    • changedInput schema / properties / pageSize / description
      Previous value: -"Results per page (1-20)"New value: +"Results per page (1-20). Default 8."
    • changedInput schema / properties / productTypes / description
      Previous value: -"Filter by product type codes (comma-separated). Values: personalAccount, savingsAccount, deposit, businessAccount, creditCard, personalVipAccount"New value: +"Filter by product type codes (comma-separated). Values: 'personalAccount', 'savingsAccount', 'deposit', 'businessAccount', 'creditCard', 'personalVipAccount'. Leave empty to show all types."
    • changedInput schema / properties / sort / description
      Previous value: -"Sort by: endTime, popularity, or reward"New value: +"Sort by: 'endTime' (default, ending soonest first), 'popularity' (most popular first), 'reward' (highest reward first)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context: promotions are time-limited, located in Poland, and include tasks, rewards, and deadlines. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exactly two sentences, front-loading the core purpose and differentiation. Every clause earns its place: the first defines the tool, the second handles alternatives and usage hints. No redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (5 params, no required fields, complete schema) and strong annotations, the description covers the essentials: what it does, how it differs from siblings, and a usage pattern. A mention of return format would be nice, but with no output schema, it is not mandatory.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides 100% coverage for all five parameters, thus the baseline of 3 applies. The description's comment 'Call with no filters to get all active promotions' adds a small usage nuance but does not significantly enhance the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches time-limited bank promotions in Poland, specifying the resource (promotions) and scope (time-limited, tasks, rewards, deadlines). It also explicitly distinguishes from permanent product offers by naming sibling tools, making its purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use Search*Accounts/SearchDeposits for permanent offers, providing a clear alternative. It also gives a practical usage pattern: 'Call with no filters to get all active promotions,' which guides when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rozbij Bank - Polish bank offers toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources