Skip to main content
Glama
Sign In

Wenbu · 问卜

by app.wenbu
OverviewDiscussionsAdmin

read library

read_library
Read-onlyIdempotent

Read a complete Wenbu guide or symbol by search_library ID. Handbook guides return Markdown, outline and export links without truncation. Optionally provide a section ID from the outline; the returned scope makes partial reads explicit. A corrected stale citation returns source_superseded with a current-document read action, not withdrawn content or read evidence. External reference entries are metadata only; use your host browsing capability to verify them.

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": "read_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
localeNoen
sectionNo

Output Schema

NameRequiredDescriptionDefault
linksNo
scopeYes
formatYes
sourceYes
contentYes
outlineNo
sectionYes
truncatedYes
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "content": {
+      "type": "string"
+    },
+    "documentId": {
+      "type": "string"
+    },
+    "format": {
+      "enum": [
+        "text/plain",
+        "text/markdown"
+      ],
+      "type": "string"
+    },
+    "links": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "outline": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "scope": {
+      "enum": [
+        "full",
+        "section"
+      ],
+      "type": "string"
+    },
+    "section": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "additionalProperties": {},
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "readAt": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "title",
+        "url",
+        "readAt"
+      ],
+      "type": "object"
+    },
+    "truncated": {
+      "const": false,
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "source",
+    "documentId",
+    "content",
+    "format",
+    "scope",
+    "section",
+    "truncated"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the read-only annotations by describing return content, no truncation, outline/export links, partial-read scope, stale-citation behavior via source_superseded, and the metadata-only nature of external references. These are concrete behavioral details an agent would otherwise not know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded, starting with the core action and ID source before covering optional section behavior and edge cases. Every sentence adds useful operational context without repetition.

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?

With annotations covering safety and an output schema covering return shape, the description is largely complete for invocation and edge cases. The main remaining gap is the unexplained locale parameter, which matters for a multilingual library.

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 description coverage is 0%, so the description must carry parameter meaning. It clarifies the required id as a search_library ID and section as an outline-derived partial-read selector, but it does not explain the locale parameter at all.

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: reading a Wenbu guide or symbol by search_library ID. It clearly distinguishes this tool from search_library by explaining that this is the read step after obtaining an ID.

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?

Explains that the ID comes from search_library and that an optional section ID from the outline enables partial reads. It also directs external reference entries to host browsing, though it does not explicitly state when not to use this tool.

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

All Wenbu · 问卜 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources