Skip to main content
Glama
Sign In

Joeb

by com.joebapp
OverviewDiscussionsAdmin

Get account overview

get_account
Read-only

See the user's Joeb plan, how much of its autofill allowance is used and when it resets, and their counts.

Returns a line each: Plan: {free|pro} Autofill used {today|this billing period}: {n}% of the plan's allowance. It resets {date} {time} UTC. Payment: {only when a subscription payment failed} Saved jobs: {n} liked, {n} applied, {n} dismissed. ... Blocked companies: {n}. Autofill is Joeb filling in job applications with AI, through its browser extension. Each plan allows so much of it, and the reply gives the share used, never an amount: the Free plan's allowance resets every day at midnight UTC, the Pro plan's at the end of each billing period. So "how much autofill is left" is 100% less the share used, until the reset.

A Payment line means a payment for the user's subscription failed: the plan reads free until the payment goes through. Tell the user to update their payment method in the Joeb web app, not to upgrade.

The counts are of list_saved_jobs' lists, and of list_blocked_companies' blocks, except that liked counts only the postings still open, as the Joeb web app's badge does: the liked list also keeps the postings employers have taken down, so its total can be higher.

No tool changes the plan or billing.

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": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description explains the exact response line format, payment-failure semantics, plan status during failed payment, reset cadence differences between Free and Pro, and the discrepancy in liked counts versus total liked postings. It also states that no tool changes plan or billing and advises updating the payment method rather than upgrading, which materially guides agent behavior.

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 description front-loads the purpose and then presents the return format in a structured line-by-line way. It is somewhat long and repeats domain explanation, such as clarifying that autofill is reported as a percentage rather than an amount, but the added context is mostly useful for interpreting the response.

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?

There is no output schema, so the description must carry return-value semantics; it does so thoroughly by explaining each response line, the payment line condition, the reset rules, and the count caveats. Combined with annotations covering read-only and closed-world behavior, the definition is complete enough for an agent to call and interpret it correctly.

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 has zero parameters, so there are no parameter meanings for the description to clarify. The empty input schema makes this baseline score appropriate.

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 and scope: the user's Joeb plan, autofill allowance usage and reset, and account counts. It distinguishes this from sibling list tools by framing the response as an account overview and explaining that the counts derive from list_saved_jobs and list_blocked_companies.

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

Usage Guidelines3/5

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

The description makes the intended use inferable through what it returns, and it names list_saved_jobs and list_blocked_companies as the underlying lists. However, it never explicitly says when to call get_account versus those sibling tools, nor does it state exclusions or direct account-level questions here rather than to a list tool.

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

All Joeb 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