Skip to main content
Glama

setup

Collects your job search profile including name, target roles, salary floor, remote-only preference, location, dealbreakers, GitHub URL, and resume. Overwrites existing profile only with confirmation.

Instructions

Onboard the user by collecting their job search profile. Captures: name, current_role, target_roles (list), salary_floor (integer), remote_only (bool), location, dealbreakers (list), github_url, resume_path. If a profile already exists, the 'confirm_overwrite' parameter must be true to replace it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull name
locationYesCurrent location or preferred location
github_urlYesGitHub profile URL (e.g. https://github.com/username)
work_styleNoWork style preferences
remote_onlyYesWhether the user only wants remote positions
resume_pathNoAbsolute path to resume file (.txt, .md, or .docx). Optional if resume_text is provided.
resume_textNoResume content as plain text or markdown. Use this instead of resume_path for portability.
current_roleYesCurrent job title or situation
dealbreakersYesList of dealbreakers (things the user will not accept)
linkedin_urlNoPublic LinkedIn profile URL for supplemental work history (optional)
salary_floorYesMinimum acceptable salary (integer)
target_rolesYesList of roles the user is targeting
optimizing_forNoWhat the candidate prioritizes: comp, growth, stability, remote, interesting_problems, autonomy
unlisted_skillsNoSkills the candidate has but aren't formalized on resume
confirm_overwriteNoMust be true to overwrite an existing profile
developing_skillsNoSkills actively being learned -- signals trajectory
dealbreaker_detailNoDetailed dealbreakers with hardness levels and notes
rejection_patternsNoTypes of roles that looked good but weren't, and brief reason why
Behavior2/5

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

No annotations provided, so description must fully convey behavior. It mentions capturing profile and overwrite guard, but does not disclose side effects (e.g., creation vs. overwrite, reversibility, authentication needs, or rate limits).

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?

Two concise sentences with front-loaded purpose. No wasted words, efficient communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 18 parameters, nested objects, and no output schema. Description is brief, omitting return values, behavior after setup, and any post-conditions. Incomplete for the complexity.

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%, baseline 3. Description only highlights a subset of parameters and adds context for confirm_overwrite (must be true to overwrite). Does not fully compensate for the high parameter count.

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?

Description clearly states it's for onboarding by collecting a job search profile. Lists key fields and overwrite behavior. Distinguishes from sibling tools like get_profile (read-only) and update_profile (modification).

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?

Implies use for initial setup, mentions overwrite condition, but lacks explicit guidance on when to use this vs. alternatives like update_profile for edits. No when-not-to indications.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarmstrong158/skillmatch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server