Skip to main content
Glama

AIApply

Get AIApply setup status

get_setup_status
Read-onlyIdempotent

Use this when the connected user wants AIApply to apply for them, and again whenever they come back to it: it says what is still missing — their resume, their confirmed job preferences, or applying being active on the account — and next_step names the one thing to do now. Follow message. setup.suggested holds the values read from their resume, for the user to confirm. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one.

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_setup_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
linksYes
setupYes
resumeYes
messageYes
next_stepYes
can_searchYesWhether AIApply searches for and queues jobs for this user.
search_onlyNoA period in which AIApply searches for jobs for this account without applying to them, if one was set up.
applying_activeYesWhether applying is active on this account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: an AIApply account is required and calling it without a signed-in user triggers a sign-in/create-account prompt. That is useful, but it does not cover rate limits, caching, or what happens to stale setup data.

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?

Usage guidance is front-loaded and every clause carries information: trigger, re-check condition, missing-item list, next_step, message, suggested values, auth requirement. It is dense and runs long as a single block, which slightly hurts scannability.

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?

For a zero-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: when to call it, that it is safe and idempotent, the auth prerequisite, and how to interpret the returned fields. Nothing material is missing.

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, so the baseline is 4. The description correctly spends no space on parameter syntax and instead explains the shape of the response fields (message, next_step, setup.suggested).

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

Purpose4/5

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

The description states a specific verb and resource: it reports what is still missing in the AIApply setup (resume, confirmed job preferences, applying being active) and names the single next action. It is clearly a status-read tool, distinguishable from save_auto_apply_setup and get_auto_apply_preferences, though it never names a sibling explicitly.

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 a concrete trigger — 'when the connected user wants AIApply to apply for them' — plus a re-entry condition ('again whenever they come back to it'). It does not state when not to use it or point to an alternative tool, so it stops short of full routing guidance.

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.

Resources