Home Renovation Free Tools
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | List the categories with a description and the number of tools in each. |
| search_toolsA | Find free home renovation tools for a task: material or cost calculators (paint, tiles, flooring, concrete, drywall, roofing, insulation, HVAC, electrical, solar), contract and estimate templates, room planners and 3D design, contractor directories and company checks (USA, UK, Poland), measuring and colour-preview apps, forums. Queries may be in English or Polish. |
| get_toolA | All details of one tool by id: English and Polish links, app store links, descriptions in both languages and every rating with its source and date. |
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 function: list_categories enumerates categories, search_tools finds tools by query, and get_tool fetches full detail for a single id. There is no overlap—an agent can unambiguously pick the right tool for browsing versus searching versus drilling into a specific item.
All three names follow a clean verb_noun snake_case pattern (list_categories, search_tools, get_tool), with the domain noun consistently referring to tools/categories. This is a fully predictable convention.
Three tools form a minimal but coherent surface for a read-only directory service: browse categories, search, and fetch details. It is slightly thin—there is no equivalent of a plain 'list all tools'—but each tool clearly earns its place.
For a read-only tool directory, the list/search/get trio covers the essential browse-and-inspect lifecycle, and search_tools even documents edge cases like empty results and bilingual queries. Minor gaps like bulk listing or filter facets exist but are workaround-able via search.