Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
waas_auth_statusB

Check Work at a Startup login session (~/.waas-mcp/storage-state.json or cookie.txt).

waas_get_profileA

Fetch your live Work at a Startup candidate profile: experience, education, skills, share copy (short_phrase / looking_for / proud_project), and role/location preferences. Requires login.

waas_preview_profileA

Fetch the founder/company-facing rendering of your WAAS profile (same data as the in-app Preview iframe): headline, share copy, pretty experience/education strings, skills, and links. Use after edits to QA without asking the user to click Preview. Requires login.

waas_update_profileA

Write Experience/Education, Skills, and/or Share on your WAAS profile. Experience helpers: fix_dates, set_current, rename, remove_match, remove_ids, order. dry_run=true by default — returns a before/after diff. Only set dry_run=false after explicit user approval. Requires login.

waas_edit_shareA

Update short_phrase / looking_for / proud_project with validation. dry_run=true by default. Same write path as waas_update_profile share fields. Requires login.

waas_edit_skillsA

Replace or merge WAAS top skills (max 10) with beginner|intermediate|advanced ratings. dry_run=true by default. Requires login.

waas_draft_profileA

Build a paste-ready Experience/Education/Share/Skills update payload from local optimized WAAS markdown drafts and/or resume/bank files. Does not write live — returns update_payload for waas_update_profile dry_run. Requires login only when compare_live is true (default).

waas_audit_profileA

Diagnose weak/missing/wrong profile entries. Returns gaps[], wrong_dates[], demote_or_remove[], suggested_order[], plus share/skills notes. Optional source_paths (resume/checklist markdown) and expect[] names for gap detection. Requires login.

waas_application_quotaA

Check Work at a Startup weekly in-app application cap (10/week). Counts candidate messages since Monday from /api/conversations, merged with ~/.waas-mcp/applied.json for recent MCP submits.

waas_searchB

Search YC Work at a Startup jobs with structured filters. Builds the search URL automatically. WORKFLOW (required):

  1. waas_application_quota (or waas_search weeklyQuota) — check remaining in-app applications this week (cap is 10).

  2. waas_search with structured filters (or waas_get_job from a URL the user provides).

  3. waas_get_job + waas_get_company for full context.

  4. waas_inspect_application — returns applicationType, fields[], weeklyQuota, applyBlocked.

  5. If applicationType=weekly_limit_reached or applyBlocked=true → stop; do NOT submit.

  6. If applicationType=external → report link/email to user; do NOT auto-submit.

  7. If applicationType=needs_login → tell user to run npm run login.

  8. Draft answers for every required field in fields[].

  9. waas_submit_application with dry_run=true — show the user all answers.

  10. Only after explicit approval → dry_run=false. Never auto-submit. Skip already_applied jobs.

waas_get_jobA

Fetch full job posting (description, comp, visa, skills). Works logged out for public pages. WORKFLOW (required):

  1. waas_application_quota (or waas_search weeklyQuota) — check remaining in-app applications this week (cap is 10).

  2. waas_search with structured filters (or waas_get_job from a URL the user provides).

  3. waas_get_job + waas_get_company for full context.

  4. waas_inspect_application — returns applicationType, fields[], weeklyQuota, applyBlocked.

  5. If applicationType=weekly_limit_reached or applyBlocked=true → stop; do NOT submit.

  6. If applicationType=external → report link/email to user; do NOT auto-submit.

  7. If applicationType=needs_login → tell user to run npm run login.

  8. Draft answers for every required field in fields[].

  9. waas_submit_application with dry_run=true — show the user all answers.

  10. Only after explicit approval → dry_run=false. Never auto-submit. Skip already_applied jobs.

waas_get_companyB

Fetch company profile, founders, and open roles.

waas_inspect_applicationA

Inspect how to apply: returns applicationType, required fields (message, resume URL, multiple choice, etc.), external apply hints, and whether you're already applied. WORKFLOW (required):

  1. waas_application_quota (or waas_search weeklyQuota) — check remaining in-app applications this week (cap is 10).

  2. waas_search with structured filters (or waas_get_job from a URL the user provides).

  3. waas_get_job + waas_get_company for full context.

  4. waas_inspect_application — returns applicationType, fields[], weeklyQuota, applyBlocked.

  5. If applicationType=weekly_limit_reached or applyBlocked=true → stop; do NOT submit.

  6. If applicationType=external → report link/email to user; do NOT auto-submit.

  7. If applicationType=needs_login → tell user to run npm run login.

  8. Draft answers for every required field in fields[].

  9. waas_submit_application with dry_run=true — show the user all answers.

  10. Only after explicit approval → dry_run=false. Never auto-submit. Skip already_applied jobs.

waas_submit_applicationA

Submit application answers. Pass a map of field names → values (see waas_inspect_application fields). Default dry_run=true. WORKFLOW (required):

  1. waas_application_quota (or waas_search weeklyQuota) — check remaining in-app applications this week (cap is 10).

  2. waas_search with structured filters (or waas_get_job from a URL the user provides).

  3. waas_get_job + waas_get_company for full context.

  4. waas_inspect_application — returns applicationType, fields[], weeklyQuota, applyBlocked.

  5. If applicationType=weekly_limit_reached or applyBlocked=true → stop; do NOT submit.

  6. If applicationType=external → report link/email to user; do NOT auto-submit.

  7. If applicationType=needs_login → tell user to run npm run login.

  8. Draft answers for every required field in fields[].

  9. waas_submit_application with dry_run=true — show the user all answers.

  10. Only after explicit approval → dry_run=false. Never auto-submit. Skip already_applied jobs.

waas_list_appliedA

List jobs you've submitted via this MCP (local tracker at ~/.waas-mcp/applied.json).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 15 tools

Disambiguation4/5

Tools cluster into profile management and job application workflows, but waas_get_profile vs waas_preview_profile and waas_update_profile vs waas_edit_skills/waas_edit_share create some boundary confusion. Descriptions do differentiate them (live data vs rendered QA, bulk write vs targeted edits), so most selections are clear.

Naming Consistency4/5

All tools share the waas_ prefix and mostly use verb_noun patterns like preview_profile, update_profile, and inspect_application. A few are noun phrases (waas_application_quota, waas_auth_status) or a bare verb (waas_search), which breaks the pattern but remains readable.

Tool Count4/5

Fifteen tools cover both profile editing and job application workflows, which is appropriate for the server's scope. It is at the high end of the ideal range, and some tools like waas_edit_skills and waas_auth_status could be folded into others, but each has a defensible purpose.

Completeness4/5

The profile surface is thorough: get, preview, audit, draft, update, and targeted edits. The job application flow is fully covered from search through inspection to dry-run submission, though there is no tool for viewing recruiter conversations or withdrawing applications.

Maintenance

ActivityMaintained
ResponsivenessResponsive