chase__balance_check
[chase · risk:low] Read the current balance of a Chase account (read-only)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | The Chase account to check (defaults to primary) |
gateway
by ai.duvera
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states 'read-only', but lacks disclosure on authentication, error handling, caching, or side effects beyond that.
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?
Single line, front-loaded with risk tag, every word necessary. No fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so description could explain return format (e.g., number with decimals). It does not, but for a simple read, this is minimally adequate.
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?
Schema coverage 100% and parameter description adequately explains default behavior. Description adds no extra meaning beyond schema, so baseline 3.
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?
Description clearly states verb 'Read', resource 'current balance of a Chase account', and notes read-only. Distinct from sibling tools which are non-financial or different finance tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use or not use this tool vs alternatives. No exclusionary language or context about when to prefer other tools like transaction history.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool is prefixed with its service name, and within each service, tools have distinct actions (e.g., mail_read vs. availability_find). The duvera tools cover different subdomains like dev, finance, and food with no overlap, making selection unambiguous.
Naming Consistency4/5
All tools follow the pattern service__action_object or service__category_action, using lowercase with underscores. The order of verb and noun varies slightly (e.g., package_track vs. boardingpass_show), but the naming is highly predictable and readable.
Tool Count4/5
With 52 tools, the server is large but justified as a gateway aggregating many external services. Each tool corresponds to a common task for its service, so no tool feels extraneous, though the total number is high.
Completeness3/5
The tool surface covers a wide array of services but only provides one or two basic operations per service (mostly read-only). While this suits a quick-lookup gateway, deeper workflows (e.g., creating or updating resources) are missing, leaving gaps for many use cases.