CareerProAI

careerpro_bank_get

Read-onlyIdempotent

Returns base.json rules, visa rules and the profile block the desktop helper writes next to the runners. Only an approved bank is returned; approval happens once on careerpro.tech/auto-apply. Pricing: {"unit": "call", "price_usd": 0, "free_quota": "200 per day per IP", "note": "Keyed volume pricing is published at https://careerpro.tech/pricing.json"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "careerpro_bank_get"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds real value on top: an authorization precondition (approval required, performed out-of-band on careerpro.tech/auto-apply), the origin of the data (written by the desktop helper next to the runners), and a rate/quota limit of 200 calls per day per IP. It does not explain what happens when the bank is unapproved (empty result vs. error), which is the main remaining gap.

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

Conciseness4/5

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

The return contents are front-loaded in the first sentence and the pricing/quota block is compact and machine-readable. The embedded pricing JSON is slightly noisy for a description field, but every sentence carries usable information and nothing is redundant.

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?

With no output schema and no parameters, the description carries the burden of explaining returns, and it does name the three constituent parts plus the approval precondition and quota. What is missing is any sense of the shape of the returned data or the failure mode for an unapproved bank, but for a simple parameterless getter this is close to sufficient.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level meaning is missing.

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

Purpose3/5

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

The description states a specific retrieval verb and enumerates three artifacts returned (base.json rules, visa rules, profile block), which is more than a restatement of the name. However, key terms like "bank" and "runners" are undefined domain jargon, so an agent cannot confidently tell what resource this is versus siblings such as careerpro_pack_get or careerpro_resume_get.

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?

The only conditional information is the approval gate ("Only an approved bank is returned; approval happens once on careerpro.tech/auto-apply"), which is a prerequisite rather than usage guidance. There is no statement of when to call this versus the other *_get siblings, no ordering advice, and no exclusion criteria.

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

All CareerProAI tools Inspect

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

Need Help?