cheap-eyes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHEAP_EYES_OPENROUTER_KEY | Yes | Your OpenRouter API key, with its own daily limit. The key goes in the env var CHEAP_EYES_OPENROUTER_KEY, never in the config file. |
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 |
|---|---|
| eyes_runA | Hand reading by meaning over large text (logs, archives, long documents, web pages) to a cheap model; quotes and line refs come back checked against the source. For exact values, structure or files under ~30 KB use mode grep ($0) or your own file tools. Each call is a paid job within daily_budget_usd; full result via eyes_result. |
| eyes_resultA | Read an eyes_run result by the id from its header: pages, grep, check report, the source text to verify a quote; cancel: true aborts a running job. No model call, free. |
| eyes_statsA | Spend today and all-time, budget left, OpenRouter key limit; models: true adds the model table. Check it before a large job or when eyes_run hits the budget. Free. |
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 3 tools
Each tool has a clearly distinct role: eyes_stats monitors spend/budget, eyes_run launches a reading job, and eyes_result retrieves or cancels it. The descriptions make the workflow boundaries explicit, so an agent can pick the right one without confusion.
All three tools follow a strict prefix_noun pattern (eyes_stats, eyes_run, eyes_result) in consistent snake_case. The shared 'eyes_' prefix aids grouping while the suffixes stay distinct.
Three tools cover the core lifecycle (check budget, run job, fetch/cancel result) with no redundancy and each earning its place. It is on the lean side, but the scope is narrow enough that this is reasonable rather than thin.
The surface covers the essential flow: budget check, job execution, result retrieval, and cancellation. A way to list or revisit prior jobs/history is absent, which is a minor gap an agent can mostly work around via the run header id.