open-jobsite
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 |
|---|---|
| create_projectB | Create a new local project. Use a lowercase, non-sensitive project_id. |
| record_site_evidenceC | Record sourced evidence locally; this performs no upload. evidence_type must be document, measurement, note, photo, receipt, sketch, or voice_transcript. publication_status must be private, synthetic, or permission_cleared. |
| get_projectA | Read the complete local project record. |
| calculate_surface_areaA | Calculate rectangular area in square feet, including a stated waste factor. |
| calculate_concrete_volumeC | Calculate cubic yards for a uniform rectangular pour; not engineering advice. |
| calculate_sheet_countB | Calculate whole sheet count with explicit sheet dimensions and waste. |
| calculate_linear_piecesC | Calculate whole stock pieces for a linear requirement. |
| draft_daily_logC | Save a draft daily log with worker identifier, role, and hours entries. |
| draft_estimateA | Save an auditable draft estimate; never send, approve, or accept it. Each line item requires description, quantity, unit, and unit_cost, with an optional evidence_ids array. |
| draft_change_orderC | Save a draft change order with structured lines and an approval gate. |
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 10 tools
Each tool targets a distinct construction or project-management action: four different calculation types, project creation/reading, evidence recording, and three distinct drafting operations. There is no meaningful overlap between the calculation tools or draft tools because the descriptions clearly differentiate their inputs and outputs.
All tool names follow a consistent snake_case verb_noun pattern, such as calculate_concrete_volume, create_project, record_site_evidence, and draft_estimate. This makes the tool set predictable and easy for an agent to navigate.
Ten tools is well within the ideal range and fits the server's scope: calculations, project records, evidence, and draft documents. Each tool has a clear purpose and none feel redundant or excessive.
The core workflow is well covered: create and read a project, record evidence, draft logs/estimates/change orders, and perform common material calculations. However, there are no update/delete project operations or direct evidence retrieval/list endpoints, which leaves minor workflow gaps.