Skip to main content
Glama
Sign In

Foliyo

by io.foliyo
OverviewDiscussionsAdmin

Save a design guide

save_guide
DestructiveIdempotent

Save or replace a named design guide in the workspace from supplied markdown and an optional source URL. Stores reusable typography, colour and layout rules. Does not visit the source URL, extract website assets or change published pages.

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": {
      "name": "<name>",
      "markdown": "<markdown>"
    },
    "name": "save_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPicker handle, e.g. "vanar". Lowercase; reused names update in place.
sourceNoWhere it came from, usually the website's URL.
markdownYesThe guide itself. Token values and rules, not a full stylesheet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=false; the description reinforces and clarifies these by saying reused names update in place and that the source URL is not fetched. It stops short of describing the response or what happens to a guide's prior contents on replace.

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?

Three short sentences, front-loaded with the action and scope, followed by a compact negative-scope clause. No filler and nothing redundant.

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 simple three-parameter tool with rich annotations and full schema coverage, the definition covers action, overwrite semantics and exclusions adequately. The only small gap is that there is no output schema and the description doesn't say what a successful save returns.

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 name, source and markdown in detail. The description only restates that markdown is supplied and source is optional, so the baseline of 3 applies with no meaningful added semantics.

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?

States a specific verb and resource ('Save or replace a named design guide in the workspace') plus the payload ('from supplied markdown and an optional source URL'). It doesn't name a sibling such as brand_guide or delete_guide, so the agent must infer the distinction, which keeps it from a 5.

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?

The phrase 'save or replace' tells the agent that reusing a name overwrites an existing guide, giving a clear condition for use. The negative scope sentence ('does not visit the source URL, extract website assets or change published pages') works as when-not guidance, though no alternative tool is offered by name.

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