Skip to main content
Glama
Sign In
Digital Life Library MCP Server

Digital Life Library MCP Server

by August-lky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

library_save

Save a meme or slang term with its meaning, source, and context for later lookup; duplicates are skipped and personal information is not stored.

Instructions

把你弄懂的一个梗用自己的话存进图书馆，下次就能直接查到。要写：梗的名字、一句话意思（80 字以内，用自己的话），以及在哪碰到的（where，比如哪个群、哪个视频）；如果是自己去搜到的，可以附上网址（url）。不要存别人的号码、手机号、邮箱这类个人信息，也不用抄整段歌词（歌词不收，抄了的那部分不会存）。已经有的梗不会重复存。

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": {
      "name": "<name>",
      "brief": "<brief>"
    },
    "name": "library_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo查到的网址（可选）
nameYes
briefYes一句话意思，80 字以内，用自己的话
whereNo在哪碰到的
originNo出处或来历（可选）
aliasesNo另外的写法（可选）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: PII is rejected, whole-lyrics copying is silently dropped ('抄了的那部分不会存'), and existing entries are not duplicated. It omits what a successful save returns and whether duplicates produce an error or the existing record.

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-loads the purpose, then the required fields, then the prohibitions — a sensible order for an agent. The lyric rule is stated twice ('不用抄整段歌词（歌词不收...）'), a minor redundancy in an otherwise dense, purposeful block.

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 6-parameter write tool with no annotations and no output schema, this covers the required fields, the optional url condition, content prohibitions, and duplicate handling. What's missing is return behavior on success or on a duplicate hit, which the absent output schema leaves unaddressed.

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 already 83%, and the description still adds meaning: 'brief' must be in your own words under 80 characters, 'where' should be a concrete venue like a group or video, and 'url' only applies when you searched it yourself. 'origin' and 'aliases' are left to the schema, which documents them.

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 concrete verb and resource ('把你弄懂的一个梗...存进图书馆') plus the payoff ('下次就能直接查到'), which cleanly separates it from read-side siblings like library_lookup and library_browse. An agent can identify the operation without opening the schema.

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?

Gives the triggering condition (you understood a meme and want to retrieve it later) and explicit content requirements (name, one-line meaning, where it was found). It does not name a sibling alternative or state when NOT to save beyond the dedupe note, so it stops short of a 5.

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

Deploy Server

Other Tools