Skip to main content
Glama

route_guide

Assess a job posting's application route before opening the browser, identifying whether it's an Easy Apply modal or external system, and flagging steps that require human input.

Instructions

What kind of application this job is, and what it will take.

Call this before browser_open. There is more than one way to apply, and the differences are structural: a LinkedIn Easy Apply lives entirely in a modal on the posting, while an "external" posting hands the browser to the employer's own account system, where a sign-in -- often an emailed one-time code -- stands before the first field.

Any step carrying human_required: true cannot be completed by the machine. Ask the user for those up front, in the same message as the profile questions, rather than walking into the gate and stopping there.

runs / success_rate / hardest_gate are what this route has actually done here before. A route with runs: 0 is a shape we know about but have never driven -- read its steps as a map, not as evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the output semantics (steps, human_required, runs, success_rate, hardest_gate), warns that runs: 0 means untested, and distinguishes machine-completable steps from human-required gates. This is strong context, though it does not mention side effects or error 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 is longer than average but every section earns its place: purpose, ordering, human interaction guidance, and data interpretation. It is structured clearly and front-loads the most important ordering constraint.

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?

Given the single parameter and the presence of an output schema, the description covers the key operational context: when to call it, how to treat human_required steps, and how to interpret historical route stats. It is complete enough for an agent to invoke the tool sensibly, though it omits any mention of failure or fallback behavior.

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

Parameters2/5

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

Schema description coverage is 0% and the description never explains job_url or how it should be supplied. The parameter is self-descriptive by name, but the description adds no meaning beyond the schema's existing 'Job Url' label.

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 clearly frames the tool as a route guide for a job application, explaining that it reveals what kind of application the job is and what the process will require. It differentiates the tool from browser actions by explicitly ordering it before browser_open, though it could state more directly that it returns a structured route plan.

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 an explicit usage instruction: call this before browser_open. It also tells the agent to surface human_required steps to the user up front and how to interpret low-run routes, which is practical guidance beyond just naming the tool.

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