Book Guide MCP

Overview Schema Source Related Servers Discussions Admin

skill_framework_list

Read-onlyIdempotent

Retrieve a list of named frameworks or methods associated with a book skill. Identifies structures for evidence, procedures, or tutoring within a guide.

Instructions

List named frameworks/methods for a book skill (L3). 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_framework_list"
  }
}

Input Schema

Name	Required	Description	Default
`book_id`	Yes	Skill id.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it lists 'frameworks/methods' for 'L3' skills, providing some extra context, but does not disclose further behavioral traits like pagination or authorization needs.

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?

Single sentence with two parts: purpose and safety. No wasted words, front-loaded with core action. Ideal conciseness.

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?

Given the simple parameter set (1 parameter, required) and existence of an output schema, the description adequately covers the tool's purpose and nature. Slight gap: does not specify if listing is exhaustive, but overall complete.

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 100% (parameter 'book_id' described as 'Skill id.'). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly states it lists named frameworks/methods for a book skill (L3) and is read-only. Verb 'List' and resource are specific, but does not explicitly differentiate from sibling tools like skill_framework_apply.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., skill_framework_apply, skill_curriculum). Does not state prerequisites or exclusions.

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