Skip to main content
Glama

Landed

by io.github.landedjobs

Get job application form

get_job_form

Get the application form for a job (by the jobId returned from search_jobs), so you can prepare answers before the user applies. Fields are grouped: "standard" (auto-fillable from a candidate profile via mapsTo), "screening" (free-text questions to draft from the résumé/experience), and "eeo" (leave to the user). Always free — a job's form is only reachable once you've already found the job via search_jobs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesThe jobId from a search_jobs result.

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so the description must carry the burden. It explains the grouping of fields ('standard', 'screening', 'eeo') and notes the form is 'Always free'. This adds useful behavioral context beyond the raw input schema.

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

Conciseness5/5

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

The description is concise (three sentences) with no fluff. It front-loads the purpose and then adds necessary details about field groups and prerequisites. Every sentence adds value.

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 simple parameter set and no output schema, the description covers the essential aspects: purpose, prerequisites, and structure of the form. It is sufficiently complete for an agent to use the tool effectively.

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

Parameters3/5

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

Schema coverage is 100% for the single parameter jobId, with a clear description. The tool description adds only the context that jobId comes from search_jobs, which is helpful but not significantly beyond the schema. Baseline score of 3 is 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 clearly states the tool's purpose: 'Get the application form for a job (by the jobId returned from search_jobs)'. It specifies the verb and resource, and distinguishes from sibling tools like search_jobs and get_learning_content.

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 description provides context on when to use the tool: 'so you can prepare answers before the user applies' and notes prerequisites ('only reachable once you've already found the job via search_jobs'). It does not explicitly mention alternatives, but the guidance is clear enough for a focused tool.

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

All Landed toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose: search_jobs finds jobs, get_job_form retrieves application forms, and get_learning_content provides learning materials. No overlap between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: search_jobs, get_job_form, get_learning_content.

Tool Count4/5

With only 3 tools, the server feels slightly thin, but it is well-scoped for job search and preparation. The count is appropriate for a focused domain.

Completeness4/5

The tools cover job search, form retrieval, and learning content. Missing features like application submission or user profile management are not critical given the server's role as a preparation helper. Minor gaps exist.

Resources