Skip to main content
Glama

Start the job search without a resume

start_without_resume

Set up an account that has no profile yet without a resume: the job the user is looking for and, optionally, the country. The job radar turns on and its first scan runs for that role; the first scan is not counted against the radar quota, and no resume generation is spent. Afterwards get_radar_matches lists what the scan found, get_next_step names the step, and set_radar_filters changes the role or place. The account then has no resume: analyses, cover letters and tailoring answer 'no_resume' until create_profile makes the first one from resume text or five answers. country defaults to the country the account signed up from. Returns 'already_started' and changes nothing when the account was already set up this way, 'already_set_up' when it has a profile, and 'invalid_payload' for a blank role or an unknown country code.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "start_without_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
roleYesThe role the radar searches for.
scanYesThe first scan: 'started' (results within about a minute), 'paused' (the user's search is paused), or the reason it did not start; empty when status is 'already_started'.
statusYes'started' — the account is set up without a resume and its radar searches for the role; 'already_started' — it already was, and nothing changed.
countryNoThe country searched, lowercase alpha-2 or 'anywhere'; null when the search is not tied to one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare that this is a non-idempotent, non-destructive mutation. The description adds real behavioral context on top: the first radar scan is free of quota and no resume generation is spent, and analyses, cover letters and tailoring answer 'no_resume' until create_profile runs. It also names the three failure returns, 'already_started', 'already_set_up' and 'invalid_payload', and their side effects.

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 setup and its free-scan benefit are front-loaded, then routing, then the no-resume consequence, then return codes, which is a sensible order. It runs long and repeats the country default already in the schema, which is the main waste.

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 mutation tool with an account-level side effect, the description covers preconditions, quota/credit cost, downstream behavior, follow-up tools, defaults and failure modes. An output schema exists, so return formats need not be explained, and the listed return strings are extra rather than a gap.

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 nested schema already documents role as free-form and country as an ISO 3166-1 alpha-2 code or 'anywhere' with a signup-country default, so the description's restatement is mostly reinforcement. It does add meaning beyond the schema by defining 'invalid_payload' for a blank role or an unknown country code, a validation rule the schema does not express.

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 action and resource: 'Set up an account that has no profile yet without a resume', with the required role and optional country. It distinguishes itself from create_profile, which is the path that makes the first resume, so an agent can tell these apart without opening a schema.

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?

The context that selects it is explicit: the account has no profile yet and the user has no resume, and the country defaults to the signup country. It also routes onward to get_radar_matches, get_next_step and set_radar_filters. It stops short of an explicit 'do not use when' clause beyond the already_started/already_set_up return cases.

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.