task-relay-discovery-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 |
|---|---|
| list_task_relay_jobsB | List Task Relay F1-F5 paid job contracts (discovery only; does not execute jobs) |
| find_task_relay_jobA | Find Task Relay F1-F5 contracts matching a machine need (deterministic local match only; Task Relay jobs only) |
| get_task_relay_job_contractA | Get exact public Task Relay job contract for F1-F5 (discovery only) |
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 3 tools
Each tool has a distinct verb (find, get, list) targeting different operations: matching a need, retrieving a specific contract, and listing all contracts. No overlap.
All names follow a consistent verb_noun pattern in snake_case: find_task_relay_job, get_task_relay_job_contract, list_task_relay_jobs.
Three tools is well-scoped for a discovery-focused server. Each tool serves a specific and necessary purpose without redundancy.
The tool set covers the core discovery operations: finding by need, retrieving details, and listing all contracts. No obvious gaps for the stated 'discovery only' scope.