Book Guide MCP

Overview Schema Source Related Servers Discussions Admin

skill_open

Read-onlyIdempotent

Retrieve a skill card’s table of contents summary, playbook/framework IDs, and concept count. This read-only overview prepares you for deeper exploration.

Instructions

Open a skill card + inventory (TOC summary, playbook/framework/rubric ids, concept count). Progressive disclosure: load this before deep search. Read-only.

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": {
      "book_id": "<book_id>"
    },
    "name": "skill_open"
  }
}

Input Schema

Name	Required	Description	Default
`book_id`	Yes	Skill id, e.g. avicenna-canon or socratic-method.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by detailing what data is returned (TOC summary, ids, concept count) and the usage context (progressive disclosure). No contradictory or missing behavioral traits.

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 two sentences, each serving a clear purpose: first sentence states the action and output, second provides usage context. No fluff or redundancy.

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?

Given the tool's simplicity (one parameter, annotations present, output schema exists), the description covers purpose, usage, and key behavioral aspects. It is sufficient for an agent to correctly invoke and interpret the tool.

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% with a single parameter 'book_id' already described with an example. The description does not add any additional meaning or constraints beyond the schema, so it meets the baseline for high coverage.

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 clearly states the tool opens a skill card and inventory, listing specific content (TOC summary, playbook/framework/rubric ids, concept count). It also provides a usage hint ('load this before deep search'), effectively distinguishing it from sibling tools like skill_search or skill_cite.

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?

The description explicitly advises progressive disclosure: 'load this before deep search'. This gives clear when-to-use guidance. However, it does not explicitly state when not to use or list alternatives, but the sibling context implies differentiation.

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