建設・リフォーム見積もりの誠実性を適正レンジで監査するMCP App(UI付き・出典検証込み)
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined, so disambiguation is perfect.
The single tool name follows a clear verb_noun pattern (audit_estimate), and with one tool there are no inconsistencies to assess.
The server is named 'hs-audit-app', suggesting a broader audit application, but it exposes only a single tool. This feels insufficient for the apparent scope of an audit app.
The tool covers one specific audit action (estimates), but there are no supporting operations such as retrieving past audits, listing estimates, or managing the audit process. For an app, this is a significant gap.
audit_estimateBInspect業者提示の建設・リフォーム見積額が適正かを HORIZON SHIELD の適正レンジ(souba-db)で判定し、操作できる監査カード(UI)で表示する。Japan only, JPY。
| Name | Required | Description | Default |
|---|---|---|---|
| work | Yes | 工事名(日本語)。例: 外壁塗装 シリコン | |
| quoted_price | Yes | 業者提示の金額(円)。単価建てはその単価。 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose side effects and output behavior. It says the tool 'judges' and 'displays' an audit card, but does not state whether it is read-only, what the card contains, or whether any data is modified. The phrase '操作できる' (operable) adds ambiguity about possible mutations, and no error or permission details are given.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single run-on sentence that packs together the audit logic, source database, UI display, and location/currency constraints. It is somewhat dense and could be split for clarity, but it is not overly long and contains no filler words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description should explain what the agent receives back, but it only mentions an 'audit card' UI, which is not useful for programmatic handling. It also fails to mention edge cases like invalid work names or out-of-range prices, leaving the agent without sufficient context for robust use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents both parameters with descriptions ('工事名(日本語)' and '業者提示の金額(円)'), achieving 100% coverage. The tool description does not provide additional parameter semantics beyond what the schema offers, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: it judges whether a contractor's construction/renovation estimate is appropriate using HORIZON SHIELD's appropriate range (souba-db) and displays the result in an operable audit card (UI). This provides a specific verb+resource ('判定' + '監査カード') and domain context. While there are no sibling tools to distinguish, the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when the user has a work name and quoted price, and it clarifies the geographic/currency scope with 'Japan only, JPY.' It does not explicitly list exclusions or alternatives, but since no sibling tools exist, the guidance is clear enough for selecting this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.