Landlord
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Alternative to OAuth token; pay-per-use API billing. | |
| LANDLORD_OUTPUT_DIR | No | Root directory for job outputs. | ./landlord-output |
| LANDLORD_MAX_RETRIES | No | Default max retries per tenant. | 3 |
| LANDLORD_TENANT_MODEL | No | Tenant SDK session model. | claude-sonnet-4-6 |
| CLAUDE_CODE_OAUTH_TOKEN | No | Required for Pro/Max users (from `claude setup-token`). | |
| LANDLORD_LANDLORD_MODEL | No | Decomposition + judge model. | claude-opus-4-7 |
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 |
|---|---|
| start_orchestrationA | Decompose the prompt into a plan and return job_id + plan awaiting approval. |
| approve_planB | Approve (or replace via edits) the plan for job_id and launch tenants. |
| get_statusB | Return current status, plan, and per-tenant states for job_id. |
| get_artifactsB | Return final artifacts and file lists; requires job to be done or cancelled. |
| cancelC | Cancel a running or pending job. |
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 5 tools
Each tool has a clear and distinct purpose: starting a job, approving it, cancelling, checking status, and retrieving artifacts. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case, making the set predictable and easy to navigate.
With 5 tools, the server is well-scoped. Each tool represents a necessary step in the orchestration lifecycle without redundancy.
The tools cover the full lifecycle from start to completion, including approval and cancellation. A missing list-jobs tool is a minor gap but doesn't hinder core workflows.