Gantry
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bot_inboxD | bot inbox |
| contextB | Read work context. Full is unchanged. Focused requires entry_ids, follows declared dependencies in the fixed design, and pages related discussion. Explicit omissions are not an impact analysis or approval. |
| designD | design |
| development_stateD | development state |
| eventsC | Poll durable notices from a ledger sequence cursor; deduplicate by event_id. |
| get_bot_contextD | get bot context |
| get_bot_issueD | get bot issue |
| get_change_reviewD | get change review |
| get_crew_setupD | get crew setup |
| get_design_assessmentD | get design assessment |
| get_development_stateD | get development state |
| get_evidence_viewD | get evidence view |
| get_onboardingC | Read bounded discovery, exact source manifest, prior answers and the customer-agent contract. |
| get_persistent_botD | get persistent bot |
| get_review_teamD | get review team |
| get_team_proposalD | get team proposal |
| get_validation_planD | get validation plan |
| historyD | history |
| identityC | Read the authenticated identity, without credentials. |
| impactD | impact |
| list_artifact_filesD | list artifact files |
| list_bot_issuesD | list bot issues |
| list_bot_memoriesD | list bot memories |
| list_change_reviewsD | list change reviews |
| list_crew_setupsD | list crew setups |
| list_development_statesD | list development states |
| list_onboardingsD | list onboardings |
| list_persistent_memoriesD | list persistent memories |
| list_team_messagesD | list team messages |
| openD | open |
| outcomesD | outcomes |
| product_overviewD | product overview |
| project_detailsD | project details |
| query_evidenceD | query evidence |
| read_artifact_batchD | read artifact batch |
| read_artifact_chunkB | Read one hash-verified part, at most 32 MiB. Ordinary files have only index 0. |
| related_review_contextD | related review context |
| render_evidence_viewD | render evidence view |
| restore_artifactB | Return saved bytes or metadata_only manifest. Chunked files require read_artifact_chunk; hashes cover each part and the complete file. |
| review_automation_statusD | review automation status |
| review_contextB | Read a consistent snapshot of the candidate diff, evidence, evaluations, work and review permissions. |
| reviewsD | reviews |
| session_detailsD | session details |
| stateD | state |
| studio_contextD | studio context |
| studio_inboxD | studio inbox |
| studio_libraryD | studio library |
| studio_overviewD | studio overview |
| studio_relatedD | studio related |
| studio_teamD | studio team |
| studio_workD | studio work |
| whyD | why |
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 52 tools
Several tools appear to target the same thing: get_development_state vs. development_state vs. list_development_states, get_design_assessment vs. design, get_bot_context vs. bot_inbox vs. get_persistent_bot, and a dense cluster of review tools (reviews, get_change_review, list_change_reviews, review_context, related_review_context, review_automation_status). Many tools have no description beyond their own name (open, why, design, state, impact, outcomes), so an agent has almost nothing to separate them by. A few areas (artifact reading, evidence) are distinguishable, but the duplication dominates.
The set mixes a verb_noun convention (get_design_assessment, list_bot_issues, read_artifact_chunk) with bare noun tools (history, identity, impact, design, state, events, reviews, open), and the same concept is named both ways in places (get_development_state vs. development_state). Prefix families like studio_*, list_*, and get_* coexist without a clear rule. It is readable but clearly inconsistent.
52 tools is well past the point where each one earns its place, and the set contains near-duplicate pairs that suggest consolidation rather than expansion. With 15+ tools carrying no real description, many entries feel like surface area rather than necessary capability.
Read coverage is broad across design, development state, reviews, evidence, artifacts, bots, teams, and onboarding, but the surface looks read-heavy: there are inbox/listing tools without an obvious send or post counterpart, and no clear create/update operations for designs, teams, or bots. Restore exists for artifacts but other write paths appear absent, which will force workarounds.