Skip to main content
Glama

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

Edit item details

edit_item
DestructiveIdempotent

Correct an item in THIS user's library. new_title/new_creator save a personal override visible only to them; the shared catalog entry is untouched. fields sets any other detail the app's edit form allows, also as a personal override (book: title, author, summary, genres, cover_url; movie: title, director, cast_members, poster_url, backdrop_url, release_date, runtime_minutes, plot, genres; show: title, creator, cast_members, poster_url, backdrop_url, first_air_date, last_air_date, plot, genres, networks; album: title, artist, cover_url, release_date, total_tracks, duration_minutes, genres, label; anime: title, title_english, description, genres, studios, cover_url, banner_url; and the equivalents for podcasts, games and manga). Dates are YYYY-MM-DD, lists are arrays, images are https links, null puts a field back to the catalog's value. new_external_id relinks the item to a different catalog entry, which is the correct fix when the wrong film/show/album was added (re_enrich cannot fix a wrong match, it only refetches the same entry). Errors if no change field is supplied.

Input Schema

NameRequiredDescriptionDefault
titleNoCurrent title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
fieldsNoOther details to set for this user, by field name. Values: string, number, array of strings, or null to revert to the catalog value. An unknown field is an error that lists the editable ones.
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
new_titleNoNew title (if changing)
media_typeYesType of media
new_creatorNoNew author/artist/director/creator (if changing)
new_external_idNoNew external ID to re-link item

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / fields
      Added value: +{
+  "additionalProperties": {
+    "items": {
+      "type": "string"
+    },
+    "type": [
+      "string",
+      "number",
+      "array",
+      "null"
+    ]
+  },
+  "description": "Other details to set for this user, by field name. Values: string, number, array of strings, or null to revert to the catalog value. An unknown field is an error that lists the editable ones.",
+  "type": "object"
+}
    • 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"
+}
    • changedInput schema / properties / media_type / enum
      Previous value: -[
-  "book",
-  "movie",
-  "album",
-  "show",
-  "anime"
-]New value: +[
+  "book",
+  "movie",
+  "album",
+  "show",
+  "anime",
+  "podcast",
+  "game",
+  "manga"
+]
    • changedInput schema / properties / title / description
      Previous value: -"Current title (partial match supported)"New value: +"Current title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)"
    • changedInput schema / required
      Previous value: -[
-  "media_type",
-  "title"
-]New value: +[
+  "media_type"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond the annotations: edits are personal overrides, the shared catalog is untouched, and null reverts a field to the catalog value, which meaningfully softens the destructiveHint=true signal. It also documents a concrete failure mode (error when no change field is given). It does not say what relinking via new_external_id does to existing overrides, nor what the call returns.

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?

Purpose and scope are front-loaded, which is good, but the middle collapses into one very long parenthetical enumerating ten media types' field lists, which is hard to scan and largely incompressible in prose form. Bullets or a summarized pattern would have carried the same information more cleanly.

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 7-parameter mutation tool with a nested free-form object, the description covers scope, formats, revert semantics, relinking, and error behavior well. The remaining gap is the return value, which matters because there is no output schema to fall back on.

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

Parameters5/5

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

Schema coverage is already 100%, but the description still earns credit by enumerating the editable field names per media type (book, movie, show, album, anime, plus 'equivalents' for podcast/game/manga) and by specifying value formats: YYYY-MM-DD dates, arrays for lists, https links for images, null to revert. That is meaning the schema cannot convey because `fields` is an open-ended object.

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 and resource ('Correct an item in THIS user's library') and immediately distinguishes the personal-override scope from the shared catalog entry. It also separates itself from the closest sibling by noting re_enrich only refetches the same entry, so an agent can pick between them without opening schemas.

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?

Explicit routing guidance for the trickiest decision: use new_external_id when the wrong film/show/album was added, because re_enrich cannot fix a wrong match. It also states the error condition when no change field is supplied. It does not cover when to prefer this over status/date/rating siblings such as set_dates, set_format or bulk_update_status, leaving overlap for the agent to infer.

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