lowdown-proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOWDOWN_SUPABASE_KEY | No | Supabase key used for recording interactions. Required for recording; the proxy works as a pure pass-through without it. | |
| LOWDOWN_SUPABASE_URL | No | Supabase URL used for recording interactions. Required for recording; the proxy works as a pure pass-through without it. |
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 |
|---|---|
| get_lowdownA | Get the interaction history and reputation of an agent, tool, or service. Call this before choosing between providers to make an informed decision. |
| record_interactionB | Record an interaction with an agent, tool, or service after using it. Helps build the shared reputation dataset for the community. |
| compare_toolsA | Compare multiple tools or agents by their recorded interaction data. Returns a ranked list with success rates and confidence levels. |
| get_node_statsB | Get your node's contribution stats and network position. Shows how much your proxy has contributed to the Lowdown network. |
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 mostly distinct purpose: single-entity lookup, interaction recording, multi-entity comparison, and node stats. get_lowdown and compare_tools both surface reputation data, but one targets a specific entity while the other ranks multiple entities, so confusion is limited.
All tools use consistent snake_case with a verb-first pattern: get_lowdown, record_interaction, compare_tools, and get_node_stats. The convention is predictable and readable throughout.
Four tools is well-scoped for a reputation proxy focused on checking, recording, comparing, and node-level statistics. Each tool earns its place without redundancy.
The core lifecycle is covered: check reputation before use, record after use, compare providers, and inspect node contribution. Minor gaps exist around listing/discovering entities or managing recorded data, but the primary workflows are supported.