Skip to main content
Glama
Sign In

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

Style my page

style_page
DestructiveIdempotent

Change how the user's public page looks. Anything left out stays as it is. background: grid, dots, stars, checker, stripes, notebook, hearts, plain (or image, only after they have uploaded a picture in the app). headings: classic, typewriter, poster, handwritten, pixel, standard. sections_look: open, boxes, windows (old-style windows). color: cobalt, violet, rose, coral, amber, green, teal, sky, default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "style_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNocobalt, violet, rose, coral, amber, green, teal, sky, or default
resetNotrue to go back to the plain look before applying the rest
headingsNoclassic, typewriter, poster, handwritten, pixel, or standard
backgroundNogrid, dots, stars, checker, stripes, notebook, hearts, plain, or image
sections_lookNoopen, boxes, or windows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already supply destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: omitted fields are preserved, reset restores the plain look first, and background 'image' only works after a picture has been uploaded in the app. It does not say what is destructive about the operation (e.g., whether reset wipes other customizations).

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

Conciseness3/5

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

The core behavior is front-loaded in the first two clauses, which is good. But the bulk of the text is a verbatim restatement of the enum values already present in the input schema, which adds length without adding 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 an all-optional, no-output-schema styling tool, the definition covers the partial-update contract, reset behavior, and the one real prerequisite (image upload). It stops short of stating who can call it or whether changes are visible immediately on the public page.

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 100%, so baseline is 3, but the description adds meaning beyond the schema: the 'image' background carries a prerequisite (prior upload in the app) absent from the schema, and 'windows' is glossed as 'old-style windows'. The rest largely repeats the enum lists already in the schema descriptions.

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: 'Change how the user's public page looks.' An agent can tell this is a visual/styling mutation on the user's page rather than content editing. It does not explicitly differentiate itself from nearby siblings like set_page_sections or set_headline, which also touch the page.

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?

The phrase 'Anything left out stays as it is' establishes partial-update usage, and the reset parameter is described as a before-apply reset. However, there is no explicit guidance on when to pick this tool over set_page_sections, set_headline, or pin_to_page, leaving the boundary to inference.

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

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