nomad-marketplace
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKETPLACE_API_KEY | No | Optional API key for authentication | |
| MARKETPLACE_API_BASE_URL | Yes | Base URL for the marketplace 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
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 |
|---|---|
| search_projectsB | Search public project listings by text, category and budget range. |
| get_projectB | Return one project by marketplace project id. |
| list_categoriesB | Return available project categories. |
| submit_bid_intentC | Read-only v1 stub. Prepares a bid intent without submitting or changing marketplace state. |
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 clearly distinct purpose: search_projects searches, get_project retrieves by id, list_categories lists categories, and submit_bid_intent prepares a bid. There is no meaningful overlap between any pair.
All tool names follow a consistent snake_case verb_noun pattern: search_projects, get_project, list_categories, submit_bid_intent. No deviations or mixed conventions.
Four tools is within a reasonable range for a read-only v1 surface. However, one tool is a non-functional stub, leaving only three active tools, which is slightly thin for a marketplace.
The read-only browsing tools (search, get, categories) cover discovery, but there is no actual bid submission, project creation, or lifecycle management. The submit_bid_intent stub is a dead end for any transactional marketplace workflow.