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_browse

Browse library entries by topic, source, recent additions, or random to discover meme and slang terms, then use lookup for full explanations.

Instructions

不查具体哪个梗，随便逛一逛图书馆的工具书：按话题翻（mode=topic，value 写类型，比如 谐音、引用；不写 value 就看有哪些话题）、按来源翻（mode=source，比如 自己学的、打底的数据集名）、看最近新增的（recent）、随便翻翻（random）。一页最多十条，只给名字和半句意思；想看全部再用 library_lookup 查名字。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "library_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNotopic / source / recent / random，默认 recent
pageNo第几页，默认 1
valueNo话题或来源的名字（topic / source 用）
per_pageNo一页几条，最多 10，默认 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a decent job: it discloses pagination (max ten per page), the truncated return shape ('只给名字和半句意思'), and the handoff to library_lookup for full detail. It does not state whether the tool is strictly read-only or any rate/permission constraints, which are minor for a browse operation.

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 and the when-to-use cue are front-loaded, and the mode list is compact. It is a single dense sentence pair with no filler, though the parenthetical examples make it slightly long for its content.

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?

There is no output schema, so the description must describe results, and it does: names plus a half-sentence meaning, at most ten per page, with library_lookup as the follow-up. Combined with full schema coverage, an agent has everything needed to call it 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 the baseline is 3, but the description adds real value: it explains that value takes a topic type or a source name depending on mode, gives concrete example values, and reiterates the per-page cap of ten against the schema's default of 8.

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?

The description states a specific verb and resource (browse the library reference collection) and enumerates the four browsing modes with examples. It explicitly distinguishes itself from library_lookup by saying it is for browsing rather than looking up a specific entry.

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?

It gives clear routing guidance: use this to wander, use library_lookup when you need the full entry for a name. The mode examples ('谐音、引用', '自己学的、打底的数据集名') tell the agent which mode to pick for which intent, though no explicit exclusion cases are listed.

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