Skip to main content
Glama

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

Set format

set_format
DestructiveIdempotent

Record how the user has or consumes an item. Books (the default media_type): format = print, ebook, audiobook or ereader. Games: format = physical or digital, and/or platform. Movies, shows, anime and albums: the copies they own, as formats (movie/show/anime: 4K UHD, Blu-ray, DVD, VHS, LaserDisc, Digital; album: Vinyl, CD, Cassette, Digital), stores for a Digital copy (movie/show: Apple TV, Prime Video, Movies Anywhere, Google TV / YouTube, Fandango at Home, Microsoft Store; anime adds Crunchyroll Store; album: Bandcamp, iTunes, Amazon Music, Qobuz, 7digital) and an edition note. formats and stores replace the saved lists; an empty list clears them.

Input Schema

NameRequiredDescriptionDefault
titleNoThe title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
formatNoBooks: print, ebook, audiobook or ereader. Games: physical or digital.
storesNoMovies, shows, anime, albums: where a Digital copy lives, from the lists above (kept only with Digital in formats)
editionNoMovies, shows, anime, albums: an edition note such as "Criterion" or "2014 remaster" (80 characters max); an empty string clears it
formatsNoMovies, shows, anime, albums: the physical/digital formats owned, from the lists above
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
platformNoGames only: the platform they play it on, e.g. PS5, Switch, PC
media_typeNoType of media. Defaults to book.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / edition
      Added value: +{
+  "description": "Movies, shows, anime, albums: an edition note such as \"Criterion\" or \"2014 remaster\" (80 characters max); an empty string clears it",
+  "type": "string"
+}
    • changedInput schema / properties / format / description
      Previous value: -"How the user read it"New value: +"Books: print, ebook, audiobook or ereader. Games: physical or digital."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "print",
-  "ebook",
-  "audiobook",
-  "ereader"
-]New value: +[
+  "print",
+  "ebook",
+  "audiobook",
+  "ereader",
+  "physical",
+  "digital"
+]
    • addedInput schema / properties / formats
      Added value: +{
+  "description": "Movies, shows, anime, albums: the physical/digital formats owned, from the lists above",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / item_id
      Added value: +{
+  "description": "Library item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.",
+  "type": "string"
+}
    • addedInput schema / properties / media_type
      Added value: +{
+  "description": "Type of media. Defaults to book.",
+  "enum": [
+    "book",
+    "movie",
+    "show",
+    "anime",
+    "album",
+    "game"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Games only: the platform they play it on, e.g. PS5, Switch, PC",
+  "type": "string"
+}
    • addedInput schema / properties / stores
      Added value: +{
+  "description": "Movies, shows, anime, albums: where a Digital copy lives, from the lists above (kept only with Digital in formats)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / title / description
      Previous value: -"The book title (partial match supported)"New value: +"The title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)"
    • changedInput schema / required
      Previous value: -[
-  "title",
-  "format"
-]New value: +[]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With destructiveHint=true and idempotentHint=true already declared, the description adds real context: formats and stores replace the saved lists rather than augmenting them, and an empty list clears them. It does not state that omitted fields are left untouched, which would be useful for a partial-update tool.

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?

Front-loaded with the core purpose, then the per-type detail. It is a single dense paragraph, and the long enumerations are justified because the schema references them, though the store lists run heavy.

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?

Eight optional params at full schema coverage, no output schema needed, and the description supplies the value vocabularies plus the replace-vs-clear semantics an agent needs to call this correctly.

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 goes further by enumerating the accepted format and store values per media type — values the schema itself defers to ("from the lists above"), making the description load-bearing.

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?

The description states a specific verb and resource: record how the user has/consumes an item, broken out per media type. It is clearly distinct from siblings like update_status or set_dates, though it never names the neighboring edit tool it overlaps with.

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?

Usage is implied by the per-media-type breakdown, and it explains that formats/stores replace existing lists while an empty list clears them. However, it never says when to use this versus edit_item or add_item, nor which media_type to pick when ambiguous.

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
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources