Resume Booster Job Board

This key's limits and powers

key_status

Read-onlyIdempotent

What THIS key is and may do: tier, requests left this minute, calls left today (both including this call), whether fit_resume (and engine=ranked on the data API) answers on it, and whether the apply tools would — with any blocker named: account link, Agent plan or live pass, mandate, résumé on file. On an Agent Pass: when the clock ends and how many applications are left (a pass starts at the first call other than this one). Call it first in a keyed session, and after any 'quota' or 'rate' refusal. Needs a key or a sign-in.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`key`	Yes
`docs`	No
`pass`	Yes	The account's pass, if any. Every figure is read off the pass row; nothing here is a constant.
`rate`	Yes
`apply`	Yes
`quota`	Yes
`counted`	No
`features`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 11, 2026

changedOutput schema / properties / features / properties / fit_resume / description

Previous value: -"Paid tiers and a live pass, exactly as POST /v1/fit plus the pass."New value: +"Paid tiers, a live pass, and keys of an account on the Agent plan: POST /v1/fit plus the pass and the plan."

changedOutput schema / properties / pass / properties / buy / description

Previous value: -"Where a pass is bought, signed in."New value: +"Where a pass is bought, signed in. ABSENT inside ChatGPT, whose app rules forbid purchase links."

changedOutput schema / properties / pass / required

Previous value: -[
-  "state",
-  "startsOn",
-  "buy"
-]New value: +[
+  "state",
+  "startsOn"
+]

First observedSep 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real context: this call counts toward the very counters it reports, a pass clock 'starts at the first call other than this one,' and it 'Needs a key or a sign-in.' Auth requirement and counter semantics are exactly the kind of disclosure annotations cannot convey.

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

Conciseness3/5

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

The opening clause is well front-loaded ('What THIS key is and may do'), but the body is one long run-on sentence with stacked em-dashes and parentheticals ('(and engine=ranked on the data API)', '(a pass starts at the first call other than this one)') that make it harder to parse than the information warrants. Nearly every clause earns its place, but the packaging is dense.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description nonetheless covers scope, timing of use, auth requirement, and blocker conditions. For a zero-parameter diagnostic tool, an agent has everything required to decide when and how to call it.

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 schema has zero parameters, which is the baseline-4 case per the rubric; there is no parameter behavior to disambiguate. The description correctly implies a no-argument call and adds nothing that could mislead about inputs.

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 states a specific resource (THIS key) and enumerates exactly what the tool reports: tier, per-minute/per-day remaining calls, whether fit_resume/engine=ranked answers, whether the apply tools would fire, and any blocker (account link, Agent plan, mandate, résumé on file). That enumeration distinguishes it from siblings like check_apply_support and application_status, which cover narrower questions.

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

Usage Guidelines4/5

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

It gives two explicit triggers: 'Call it first in a keyed session, and after any quota or rate refusal.' That is clear, actionable when-to-use guidance. It doesn't name a sibling as an alternative or state when not to call it, so it falls short of a full 5.

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

All Resume Booster Job Board 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.