LinkedRun
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_taskC | Register one task. Historical input refs use task:/artifact: or artifact:. |
| submit_graphC | Register a batch DAG atomically. Local refs use @task/artifact and control deps use @task. |
| get_taskB | Return task state, attempts, dependencies, and committed artifacts. |
| list_tasksC | List recent tasks, optionally filtered by state. |
| cancel_taskB | Cancel a pending or running task and invalidate its current fencing generation. |
| retry_taskA | Create a new execution generation for a failed/canceled/blocked task. |
| list_artifactsC | List immutable artifacts committed by a task. |
| get_artifactB | Resolve one task output to its immutable artifact record and local storage path. |
| get_graphC | Return the persisted dependency neighborhood around a task. |
| get_eventsC | Read durable task/artifact lifecycle events after an event ID. |
| watch_eventsC | Long-poll durable events without busy waiting; reconnect using the last event ID. |
| resource_statusA | Show configured capacity and current reservations; no resource prediction is performed. |
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 12 tools
Each tool targets a distinct resource and action: submission (single vs batch), task state management (get, list, cancel, retry), artifact resolution, graph query, event streaming, and resource status. No two tools appear to overlap in purpose.
All tools follow a consistent snake_case verb_noun pattern (submit_task, get_task, list_artifacts, watch_events, etc.). Minor exception like resource_status is still readably aligned with the convention.
With 12 tools, the surface is well-scoped for a task orchestration server. Every tool has a clear role and the count feels appropriate for the domain without redundancy or bloat.
The set covers the full lifecycle: task submission (single and DAG), state inspection, cancellation/retry, artifact access, dependency graph queries, event consumption (pull and push), and resource monitoring. No obvious gaps for common workflows.