site

House rendering cost calculator

calculate

Run the House rendering cost calculator calculator: Wall area used; Low end of typical 2026 quotes; High end of typical 2026 quotes. Missing inputs fall back to their documented defaults.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate"
  }
}

Input Schema

Name	Required	Description	Default
`area`	No	Wall area to render
`scaffold`	No	Scaffold needed?	1
`houseType`	No	House type (sets a typical wall area)	0
`renderType`	No	Render system	monocouche

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions default fallback for missing inputs, but it does not state that the tool is read-only/pure calculation, what the output format or currency is, or any assumptions behind the quote ranges.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and mostly front-loaded, but the phrasing 'calculator calculator' is redundant and the semicolon-separated list is ambiguous. It is concise but not cleanly structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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 do more to explain return values and assumptions. It names likely outputs (wall area used, low/high quotes) and default behavior, but leaves output format, currency, and calculation assumptions unclear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented in the schema. The description adds only the default-fallback behavior and does not add syntax, enum meaning, or parameter-specific guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: running the House rendering cost calculator. It also hints at the calculator's outputs (wall area used, low/high quotes), making the overall purpose clear despite the awkward 'calculator calculator' repetition and lack of explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives no guidance on when to use this tool versus alternatives such as calculator_describe. The only contextual note is that missing inputs fall back to defaults, which is behavioral rather than usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All site tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?