Skip to main content
Glama
Sign In

Renderior

by com.renderior
OverviewDiscussionsAdmin

Patio umbrella size calculator

patio_umbrella_size
Read-only

What size patio umbrella covers a table and its chairs, from the table's shape and size, and how heavy a base it needs. Gives the designer rule of thumb; the page linked in the answer shows the sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "length": "<length>"
    },
    "name": "patio_umbrella_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeNoTable shape. Default round.round
widthNoTable width in inches, for a rect table only.
lengthYesTable diameter (round), side (square) or length (rect), in inches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint=false), so the bar is lower. The description still adds real context: results are a 'designer rule of thumb' rather than an exact spec, and a linked page in the answer carries the sourcing — useful for an agent deciding how confidently to present numbers.

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

Conciseness5/5

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

Two sentences, zero filler, with the core question front-loaded and the caveat about the rule of thumb following. Nothing could be removed without losing information.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small read-only calculator with no output schema, the description adequately names both outputs (umbrella coverage and base weight) so the agent knows what comes back. The only minor gap is that output units and formatting are not indicated.

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 coverage is 100%, so the schema already documents shape, width (rect only), and length. The description confirms the inputs map to table shape and size but does not clarify the width-vs-rect dependency or units beyond what the schema states, so the baseline 3 applies.

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

Purpose5/5

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

States a specific question the tool answers ('what size patio umbrella covers a table and its chairs'), the inputs driving it (table shape and size), and a second output the name hides (base weight). That distinguishes it from every sizing sibling, which each target a different object.

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

Usage Guidelines3/5

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

Implicit usage is clear from the phrasing, and cross-sibling routing is largely unnecessary since each sibling handles a different object type. However, it gives no explicit when-to-use/when-not guidance and never acknowledges the sibling calculators directly.

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

All Renderior toolsInspect
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