workatastartup-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WAAS_COOKIE | Yes | Your Work at a Startup session cookie. Obtain it from browser developer tools after logging in. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_job | Fetch a Work at a Startup (workatastartup.com) job posting by its numeric id and return the title, company, and full description. Needs a WAAS_COOKIE holding your logged-in session. |
| get_companyA | Fetch a Work at a Startup (workatastartup.com) company by its slug and return the company's details along with the roles it currently has open. Needs a WAAS_COOKIE holding your logged-in session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is zero ambiguity. An agent will always select get_company.
The single tool name 'get_company' follows a clear verb_noun pattern. Consistent and descriptive.
A single tool for what implies a broader domain (company and role retrieval) is too thin. Ideally there would be at least listing or search capabilities.
Only a read operation exists. Missing essential operations like list, search, or any mutation endpoints, leaving obvious gaps for the domain.