web3-jobs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEB3_CAREER_API_TOKEN | Yes | Your web3.career API token (request at web3.career/web3-jobs-api) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_jobsA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_jobs_prompt | Generate a prompt for searching Web3 jobs based on role and optional location. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools. The single tool has a clear, distinct purpose that cannot be mistaken for any other functionality within this server.
The single tool follows a consistent verb_noun naming pattern (query_jobs). With only one tool, naming consistency is inherently perfect as there are no other tools to compare against or create inconsistencies with.
A single tool is too few for a server focused on Web3 job listings. While the query_jobs tool provides comprehensive querying functionality, there are obvious gaps in the surface area that would require additional tools to cover a complete job search domain.
The server is severely incomplete for Web3 job operations. While query_jobs provides robust filtering capabilities, there are no tools for viewing individual job details, applying to jobs, saving favorites, or managing user profiles. The single tool represents only a fraction of what would be expected in a job search domain.