Skip to main content
Glama
Sign In

Glazecalc

by com.glazecalcapp
OverviewDiscussionsAdmin

Substitutes for old materials

suggest_substitutes
Read-onlyIdempotent

Finds the discontinued or scarce materials in a recipe and the modern ones that replace them, then suggests amounts that keep the unity formula as near as the materials allow, as the Glazecalc app does. report.closeness says how near the new unity formula comes to the old, oxide by oxide, as match_from_materials does. Test any suggestion before using it.

Input Schema

NameRequiredDescriptionDefault
linesYesThe recipe's base materials (not colorants), at most 40 lines.
regionNoWhere the potter buys materials, so suggestions are ones sold there: US, UK, EU or AU. Leave it out for any.
languageNoThe language for any sentences in the answer, as a BCP 47 tag such as "en", "de" or "ja". Languages Glazecalc does not offer are answered in English.
allowLeadNoWhether materials with lead may be suggested. Off by default.
allowMoreNoMaterials whose suggested cap to lift, as report.capped names them: raw clay is held to 20% of the batch (or the recipe's own share) where that costs the match little.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / allowMore
      Added value: +{
+  "description": "Materials whose suggested cap to lift, as report.capped names them: raw clay is held to 20% of the batch (or the recipe's own share) where that costs the match little.",
+  "items": {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already carry read-only/non-destructive safety. The description adds real behavioral context: unity-formula preservation, the closeness report field, cap behavior on raw clay, and that suggestions are region-constrained. It doesn't describe response shape beyond report.closeness, keeping it a 4.

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

Conciseness4/5

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

Three front-loaded sentences that lead with what it does. Slightly dense with cross-references ('as the Glazecalc app does', 'as match_from_materials does'), but each clause carries 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?

No output schema, so the description must describe returns; it names report.closeness and report.capped, covering the key outputs. Reasonably complete for a 5-param tool, though the full return shape is only partially sketched.

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 parameters are fully documented in the schema and baseline is 3. The description reinforces allowMore via report.capped naming and implies the region/lead constraints, but adds little syntax or semantics beyond the schema.

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?

Specific verb+resource: finds discontinued/scarce materials in a recipe and the modern replacements, plus suggests amounts preserving the unity formula. Explicitly distinguishes itself from match_from_materials by noting report.closeness parallels that tool.

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?

'Test any suggestion before using it' gives a verification step, and the match_from_materials comparison implies when closeness matters. But there's no explicit statement of when to prefer this over analyze_recipe or match_from_materials, so usage remains implied.

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

All Glazecalc 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