Skip to main content
Glama

BotShelf Vampire

Get one item

get_item
Read-onlyIdempotent

Get one item by id (the site path from a search or list result, for example /library/claude-code/code-review/). Returns its card and, when the item has a plain file that is open without sign-up, the full text. Long text comes in parts: pass next_offset as offset to read on.

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

Input Schema

NameRequiredDescriptionDefault
idYesItem id: the site path, or the full https://botshelfvampire.com/... address of the item page.
offsetNoCharacter position to start from (default 0).
max_charsNoMost characters of text to return (default 20000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds useful behavioral detail beyond annotations: it returns a card, may return full text only when the item has a plain file open without sign-up, and explains pagination via next_offset.

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 description is front-loaded with the core operation and is only three sentences. It is efficient overall, though the phrase 'pass next_offset as offset to read on' is slightly compressed and references a response field not defined in the input schema.

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?

There is no output schema, so the description appropriately explains what is returned: a card and conditionally full text, with pagination guidance. It is complete for the core call, though it does not describe not-found or access-limited behavior.

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. The description still adds meaning by clarifying that id is a site path obtained from search or list results and that offset is used to continue reading long text via next_offset.

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 ('Get one item by id') and clearly distinguishes this single-item retrieval from the sibling list/search operations by referring to ids that come from search or list results.

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 usage context by explaining that the id is the site path from a search or list result and includes an example path. It does not explicitly name when not to use it, but the intended use after searching/listing is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.