Skip to main content
Glama
Sign In

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

Pin to my page

pin_to_page
Idempotent

Pin one of the user's titles to the top of their public page (up to 3 pins), optionally answering a prompt ("The one I'd save in a fire", or their own) and with a short line. On a title already pinned, changes its prompt or line.

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": {
      "media_type": "<media_type>"
    },
    "name": "pin_to_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoA short line of their own about it; empty clears it
titleNoExact title in their library
promptNoThe prompt the pin answers, up to 80 characters; empty clears it
item_idNoLibrary item id (UUID); use instead of title
media_typeYesType of media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
-  "book",
-  "movie",
-  "album",
-  "show",
-  "anime",
-  "podcast",
-  "game",
-  "manga"
-]New value: +[
+  "book",
+  "movie",
+  "album",
+  "show",
+  "anime",
+  "podcast",
+  "game",
+  "manga",
+  "comic"
+]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations (non-read-only, idempotent, non-destructive, open-world), the description discloses public visibility, the three-pin limit, optional prompt/line fields, and update-in-place behavior. It omits permission requirements and what happens when the pin limit is reached, but adds substantial domain behavior.

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?

Two tight clauses: the pin action with its constraints is front-loaded, followed by the update behavior. There is no filler.

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?

Covers purpose, domain rules, and mutation semantics for a five-parameter tool with full schema coverage and annotations. Missing only explicit sibling routing for removal and edge-case limit behavior, which are minor given the structured fields.

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 documents all five parameters, including empty-clears behavior and item_id versus title. The description only adds prompt examples such as 'The one I'd save in a fire' and reinforces prompt/line editing, which is marginal 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?

States a specific verb (pin), resource (one of the user's titles) and destination (top of their public page), plus the three-pin cap and update behavior. This clearly distinguishes it from unpin_from_page and other page-setting siblings.

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?

Explains the main scenario and that calling it on an already-pinned title edits the prompt or line instead of creating a duplicate. It does not explicitly route removal to unpin_from_page or clarify when to prefer item_id over title, leaving some guidance to the schema and sibling names.

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