Skip to main content
Glama

get_shelf

Retrieve details of a specific shelf and its books from BookStack wiki instances using the shelf ID.

Instructions

Get details of a specific shelf including its books

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesShelf ID

Implementation Reference

  • Handler logic for the 'get_shelf' tool: parses the shelf ID from arguments and calls the BookStack client's getShelf method, then formats the API response.
    case "get_shelf": {
      const id = parseInteger(args.id);
      const result = await client.getShelf(id);
      return formatApiResponse(result);
    }
  • Input schema definition for the 'get_shelf' tool, specifying the required 'id' parameter as a number.
    {
      name: "get_shelf",
      description: "Get details of a specific shelf including its books",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "number", description: "Shelf ID" },
        },
        required: ["id"],
      },
    },
  • Core helper function in BookStackClient that performs the API GET request to retrieve a specific shelf by ID.
    async getShelf(id: number): Promise<Shelf> {
      const response: AxiosResponse<Shelf> = await this.api.get(`/shelves/${id}`);
      return response.data;
    }
  • src/index.ts:56-59 (registration)
    Registration of content tools (including 'get_shelf') into the MCP server's allTools list, which is returned in listTools handler.
    const allTools: Tool[] = [
      ...createContentTools(bookStackClient),
      ...createSearchAndUserTools(bookStackClient),
    ];
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error conditions, or what 'details' include beyond books. For a tool with no annotation coverage, this leaves significant behavioral gaps about how the tool actually works.

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 a single, efficient sentence that immediately states the tool's core function. Every word contributes meaning: 'Get' (action), 'details' (scope), 'specific shelf' (target), 'including its books' (key output). There's no wasted text, repetition, or unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read operation with no annotations and no output schema, the description is insufficient. It mentions 'details' and 'books' but doesn't explain the return format, whether books are full objects or just references, or what other shelf details are included. The agent lacks critical information about what to expect from this tool's response.

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%, with the single parameter 'id' fully documented in the schema as 'Shelf ID'. The description doesn't add any parameter information beyond what the schema provides (no format examples, constraints, or relationship to 'books'). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('shelf'), and specifies what details are included ('including its books'). It distinguishes this from list_shelves (which would list multiple shelves) but doesn't explicitly differentiate from other get_* tools like get_book or get_user. The purpose is clear but sibling differentiation is incomplete.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing a shelf ID), when not to use it (e.g., for listing shelves), or refer to sibling tools like list_shelves or search_all. The agent must infer usage from the tool name and context alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lautarobarba/bookstack_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server