TeamTok MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check whether the MCP server is running. |
| search_entry_jobsB | Search and rank student-friendly intern, newcomer, and entry-level job postings. |
| get_job_detailC | Summarize a specific Saramin job posting by job id or URL. |
| make_application_briefC | Create an application preparation checklist for a selected job posting. |
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 4 tools
Each tool has a distinct purpose: health check, job search, job detail, and application prep. No overlap, clear differentiation.
Tools use snake_case with verbs (get_, search_, make_), but 'health_check' is a noun phrase, breaking the verb_noun pattern slightly. Consistent otherwise.
4 tools cover the core workflow (search, detail, application aid, health) without being excessive. Well-scoped for the server's purpose.
Covers search, detail, and application preparation. Missing filters or save features, but the set is sufficient for a focused job search assistant.