Skip to main content
Glama

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

List by status

get_by_status
Read-onlyIdempotent

Get items filtered by status. Books: unread, reading, finished, abandoned. Movies/shows: unwatched, watching, watched, abandoned. Anime: plan_to_watch, watching, completed, saved, on_hold, dropped (the movie words also work). Albums: unheard, listening, played, saved. Podcasts: want_to_listen, listening, caught_up, dropped. Games: unplayed, playing, played, saved, on_hold, abandoned. Pass status "all" for any media type to return items regardless of status.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 50)
statusYesStatus to filter by, or "all" to return items regardless of status
media_typeYesType of media

Output Schema

NameRequiredDescriptionDefault
itemsYes
queryNo
totalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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 / status / description
      Previous value: -"Status to filter by"New value: +"Status to filter by, or \"all\" to return items regardless of status"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Items from the user's own library matching the request.",
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "cover_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "creator": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "genres": {
+            "items": {
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "media_type": {
+            "enum": [
+              "book",
+              "movie",
+              "album",
+              "show",
+              "anime",
+              "podcast",
+              "game",
+              "manga"
+            ],
+            "type": "string"
+          },
+          "rating": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "themes": {
+            "items": {
+              "type": "string"
+            },
+            "type": [
+              "array",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "year": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "media_type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation, and the description does not contradict them. The description adds useful filtering context but does not discuss return ordering, pagination, or how the limit interacts with results.

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?

The purpose is front-loaded in the first sentence, followed by the necessary status lists. The description is somewhat long, but the enumeration is largely justified because the status schema field has no enum of its own.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and rich annotations present, the description need not explain return values or safety behavior. Still, it is incomplete for one supported media type because manga status values are not provided.

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 coverage is 100%, so the schema already documents all parameters at a baseline level. The description adds valuable status vocabulary beyond the schema, but it omits manga statuses even though 'manga' is a valid media_type in the enum.

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: get items filtered by status. It makes the tool's filtering role clear, but it does not explicitly distinguish this tool from siblings such as get_by_rating or search_library.

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 description explains how to use the status parameter, including per-media-type values and the special value 'all'. However, it does not state when to choose this tool over alternatives like get_by_rating, get_recently_added, or search_library.

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