Skip to main content
Glama
Sign In

Glazecalc

by com.glazecalcapp
OverviewDiscussionsAdmin

Search the guides

search_guides
Read-onlyIdempotent

Searches Glazecalc's plain-language guides for potters (glazing from first principles, making a glaze, safe mixing, safety at home with children and pets, firing a kiln, and a companion to John Britt's free glaze course, in English only) in the language asked for, or in English where that language has no match. Returns each matching section's title, anchor, a short excerpt, its address on the website and its resource URI, which resources/read returns in full. Use it for glaze defects, safety, firing and terms, and cite the address. Link John Britt's videos by title only; never retell, summarise or quote them.

Input Schema

NameRequiredDescriptionDefault
conesNoHow the potter fires, for the parts of the guides that differ: Orton cones (the default), SK cones (JIS R 8101) or by temperature.
guideNoOnly this guide.
limitNoAt most this many sections (5 unless asked).
queryYesWords to look for, such as "crawling", "respirator", "bisque schedule" or "specific gravity".
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / guide / enum
      Previous value: -[
-  "glazing-basics",
-  "making-a-glaze",
-  "safe-mixing",
-  "home-safety",
-  "firing",
-  "learn-with-john-britt"
-]New value: +[
+  "glazing-basics",
+  "making-a-glaze",
+  "safe-mixing",
+  "home-safety",
+  "firing",
+  "learn-with-john-britt",
+  "teaching-glaze-calculation"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / guide / enum
      Previous value: -[
-  "glazing-basics",
-  "making-a-glaze",
-  "safe-mixing",
-  "home-safety",
-  "firing"
-]New value: +[
+  "glazing-basics",
+  "making-a-glaze",
+  "safe-mixing",
+  "home-safety",
+  "firing",
+  "learn-with-john-britt"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses that results include title, anchor, excerpt, website address, and resource URI, and that resources/read returns the full resource. It also describes language fallback behavior and citation expectations, which are important operational details not present in annotations.

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?

The description is dense but front-loaded, moving from purpose to return format to special instructions. The parenthetical list of guide topics is long but useful for routing, though the overall sentence structure could be slightly tighter.

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

Completeness5/5

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

With no output schema, the description supplies the missing return-value details, including excerpts and resource URIs. It also covers language fallback, citation, and the special video-linking restriction, making it complete for this search tool.

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 the schema already explains each parameter, including the language fallback and guide enum. The description adds little parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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?

The description names a specific verb and resource ('Searches Glazecalc's plain-language guides for potters') and lists the guide scope, including the specific domains it covers. This clearly distinguishes it from sibling tools such as search_materials or analyze_recipe.

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

Usage Guidelines4/5

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

It explicitly says to use the tool for glaze defects, safety, firing, and terms, and gives a concrete citation instruction. It also states a special rule for John Britt's videos. It does not name an alternative tool for non-guide searches, but the usage context is clear.

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