Skip to main content
Glama
Digital Life Library MCP Server

Digital Life Library MCP Server

by August-lky

library_mark

Set or hide a library item's status so AI companions can stop proactively suggesting dated entries while keeping them searchable.

Instructions

给图书馆里的一条标状态:过时了(dated)、有点过气(fading)、正流行(active),也可以隐藏它。标成过时的梗不会再被主动提示,但查的时候还是找得到。

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": {
      "id": "<id>"
    },
    "name": "library_mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes条目 id(library_lookup 的结果里有)
hiddenNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose a meaningful side effect: entries marked 'dated' stop being surfaced proactively yet remain findable. However, it never says what 'hidden' actually does (fully removed from listing?), whether the call is idempotent, or whether the operation overwrites prior status, leaving the mutation profile incomplete.

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?

Two tight sentences: the action and its status vocabulary come first, then the behavioral footnote about 'dated'. No filler, though the domain-specific word '梗' is used without being tied back to what a library entry actually is.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers the status semantics well but omits any explanation of the hidden flag, the unknown enum value, and what the call returns or how to confirm success. Adequate, with clear gaps.

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 only 33%, so the description must compensate. It does useful work mapping the human names (过时了/过气/正流行) onto the enum values dated/fading/active and explains the semantic consequence of 'dated', but it leaves the 'hidden' boolean and the 'unknown' enum value entirely unexplained.

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 opens with a specific verb + resource: marking a status on a single library entry, and enumerates the valid states (dated/fading/active) plus hiding. An agent can tell this mutates entry state rather than looking things up or saving new entries. It stops short of naming which sibling (e.g. shelf_status) this supersedes or how it differs from library_save.

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 context is implied (curating the library, retiring stale entries) and the 'dated' consequence hints at when to pick that status, but there is no explicit statement of when to call this versus library_save or shelf_status, and no prerequisites or when-not conditions are given.

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