trades-runtime
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRADES_RUNTIME_URL | No | Worker origin. Default https://trades-runtime.vibelock.workers.dev |
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 |
|---|---|
| trades_runtime_healthB | Trades-Runtime giveaway health. Read-only. Does not increment counters. This public Worker holds no tenant data and never writes. Writes exist only in the local runtime on the operator machine, where each write requires operator approval and is off by default. |
| trades_runtime_statsA | Honest KV view/download counts with human/bot split. Read-only. Does not increment counters. |
| trades_runtime_citeA | Public cite.json for Trades-Runtime. Read-only. Includes local_package: the local runtime's modules (refrigerant log, permits, agreements, warranty claims, truck stock, callback root cause) and platform peers (Jobber, Housecall Pro, Square, QuickBooks Online, FieldEdge, Service Fusion, Successware, Workiz, ServiceTrade, BuildOps, FieldPulse, Kickserv, mHelpDesk, ServiceM8, Simpro, Commusoft, Wintac) with each peer's mode and mappingConfidence. They run only on the operator machine; this Worker holds no tenant data and was not tested against a live tenant. |
| trades_runtime_skillB | Agent skill markdown for the public giveaway Worker, including what the local package carries: modules, platform peers (file drop or optional read-only pull), and mapping confidence (documented / partial / guessed). Read-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 4 tools
Each tool has a distinct output type and purpose: stats for counts, health for status, cite for citation JSON, and skill for markdown documentation. However, cite and skill both describe the local package, modules, peers, and mapping confidence, creating some content overlap that could confuse an agent choosing between them.
All four tools follow the same predictable snake_case prefix pattern: trades_runtime_ plus a concise noun. The convention is uniform throughout with no mixed styles.
Four tools is reasonable for a narrow, read-only public metadata Worker. The set is slightly thin, but each endpoint serves a clear informational role and none appears redundant.
The surface covers the apparent public informational needs: usage stats, health, citation metadata, and agent skill documentation. Minor gaps may exist around version/build metadata or a root index, but the stated read-only purpose is largely covered.