FARPY
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FARPY_API_BASE | No | https://api.farpy.com | |
| FARPY_AGENT_TOKEN | Yes | FARPY agent API token |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspectA | Inspect a Blender .blend without spending. Creates upload_id and an open locked quote. |
| quoteA | Create a locked quote for a frame sub-range. Does not spend. |
| startA | ONLY spend tool. Reserves wallet cents for the locked quote_id. |
| statusA | Read normalized job state and polling guidance. No worker, provider, or progress-percent fields. |
| downloadA | Return a ZIP download URL for a completed job. Never returns ZIP bytes. Delivery tokens are not logged. |
| receiptB | Return a safe receipt subset. SHA-256 is byte identity, not artistic review. |
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 6 tools
Most tools are distinct, but inspect and quote both create quote-like objects and both explicitly do not spend, making their boundary fuzzy. Status, download, start, and receipt are clearly separated.
Names are simple, lowercase, and single-word, but they mix imperative verbs (inspect, start, download) with noun-style actions (status, receipt). There is no consistent verb_noun pattern, though the names remain readable.
Six tools is well-scoped for the quote-to-receipt rendering workflow. Each tool represents a meaningful stage in the process without redundant or unnecessary surface area.
The core lifecycle is covered: inspect, quote, start, status, download, and receipt. Minor gaps exist such as no explicit cancel/refund flow and upload is only referenced via upload_id, but agents can work around these for typical jobs.