House Rules
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_contextC | Fetches a compact git context bundle so the assistant stops asking for basic repo details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| house_rules | Reusable instructions for how I want the assistant to behave (safe, scoped, and consistent). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct as it is the only one available.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'git_context' follows a clear noun-based pattern.
One tool is too few for a server named 'House Rules', which suggests a broader scope. This minimal set feels thin and may not adequately cover the implied domain of managing or enforcing rules.
The server is severely incomplete; a single tool for fetching git context does not cover any meaningful 'House Rules' domain. There are obvious gaps, as no operations for creating, updating, or managing rules are provided.