chimeraforge
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 |
|---|---|
| chimeraforge_planB | Recommend the best (model x quantization x backend x GPU-count) deployment for a workload, or report why nothing fits. Returns candidates with per-number provenance (measured/extrapolated/estimated/unknown). Use for: 'what GPU do I need for ', 'will fit on ', 'how many GPUs for N req/s', 'what will it cost'. |
| chimeraforge_resolve_modelB | Resolve a model id to real params/architecture (grounds hallucinated specs). |
| chimeraforge_list_hardwareA | List known GPUs with VRAM/bandwidth/TDP/interconnect. |
| chimeraforge_compare_apiA | Compare self-hosting against the hosted APIs for a workload: sizes the cheapest feasible GPU fleet, prices the same traffic through each API model, and gives the monthly output-token volume where the two break even. Use for 'is it cheaper to self-host or use the API', 'when does a GPU pay for itself'. API prices come from a dated snapshot -- the result reports its age and flags it when stale; say so rather than quoting an old price as current. |
| chimeraforge_suggestA | Rank the models that actually fit and hit the SLO on a given GPU -- the inverse of planning. Use for 'what can I run on a 4090', 'best model for 12GB'. Sources: catalog (offline curated set), ollama (locally installed), hf (top Hub repos). |
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 clearly distinct purpose: model resolution, deployment planning, hardware listing, API-vs-self-host cost comparison, and inverse model suggestion for a given GPU. The most similar pair, plan and suggest, is explicitly described as inverse directions, so an agent should not confuse them.
All tools share the consistent chimeraforge_ prefix and a clear action verb, making them easy to scan. However, resolve_model, list_hardware, and compare_api follow a verb_noun pattern while plan and suggest are just bare verbs, creating a minor inconsistency.
Five tools is a compact, well-scoped surface for this server's purpose. Each tool covers a distinct part of the model-deployment decision workflow, and none of them feel redundant or extraneous.
The core workflow is well covered: resolve a model, plan a deployable setup, list available hardware, compare hosting costs, and find models that fit a GPU. A minor gap is that API price snapshots and model catalogs are exposed as static sources without an explicit refresh tool, but staleness is at least reported and flagged.