Skip to main content
Glama

Foliyo

by io.foliyo
OverviewDiscussionsAdmin

Check a Foliyo before publishing

preflight_html
Read-onlyIdempotent

Validate HTML (static by default, or interactive:true for the sandboxed mode) and inline explicit image/font/CSS assets without publishing. Returns ready and issues; the prepared HTML is returned only when includeHtml is true. publish_html runs the same checks, so this is optional. Does not visually render or fetch external URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExisting page to check for accidental content removal.
htmlYes
assetsNo
includeHtmlNoAlso return the prepared HTML. Off by default to keep the reply small.
interactiveNoCheck as an interactive page (scripts kept, sandbox rules applied) instead of static.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / includeHtml
      Added value: +{
+  "description": "Also return the prepared HTML. Off by default to keep the reply small.",
+  "type": "boolean"
+}
    • addedInput schema / properties / interactive
      Added value: +{
+  "description": "Check as an interactive page (scripts kept, sandbox rules applied) instead of static.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Existing page to check for accidental content removal.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld=false), the description adds output behavior ('returns ready and issues'), a conditional return ('prepared HTML only when includeHtml is true'), and explicit non-behaviors ('does not visually render or fetch external URLs'). The no-external-fetch statement is consistent with openWorldHint=false, so there is no contradiction.

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?

Four tight sentences, front-loaded with the core purpose and mode behavior, followed by return semantics and exclusions. Every sentence carries distinct information and none is redundant.

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 present, the description correctly shouldered the burden of describing returns (ready, issues, conditional HTML) and the non-rendering/non-fetching boundaries. For a 5-parameter read/validation tool, nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

Schema coverage is 60%, and the description meaningfully supplements it by explaining the static-default vs sandboxed interactive mode and the asset-inlining behavior of the assets array. It does not touch the id parameter (accidental-removal check), so it stops short of full coverage.

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 verb (validate/inline) on a specific resource (HTML plus image/font/CSS assets), with scope explicitly bounded by 'without publishing'. It also names the sibling it overlaps with (publish_html), so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says 'publish_html runs the same checks, so this is optional', which tells the agent both the alternative and the condition under which this tool is warranted. The static-vs-interactive:true framing further guides when each mode applies.

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

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