Skip to main content
Glama

BotShelf Vampire

Search the shelf

search_items
Read-onlyIdempotent

Search BotShelf Vampire items by words. Every word must match the title, description, where-it-runs, topic or keywords. Returns short cards; call get_item for the full text.

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": {
      "query": "<query>"
    },
    "name": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoKind of item, for example team, build, toolkit, grokbot, trade, guide, field. list_items returns the kinds that exist.
limitNoHow many results (default 10).
queryYesWords to look for, for example "code review" or "meeting notes".
topicNoTopic label exactly as shown on the shelf, for example "Research".
accessNoopen = full text readable without sign-up. paid = listed, text not available here.
checkedNotrue = only items with a recorded check.
runs_onNoWhere it runs, exactly as shown on the shelf, for example "Claude Code", "Grok Bot", "Ollama", "TradingView".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the conjunctive all-words-must-match rule across five fields, and the fact that results are abbreviated cards rather than full text — the key thing an agent needs to know to avoid assuming it got the content.

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?

Three short sentences, zero filler, and the essential matching semantics and the get_item hand-off are both front-loaded. Nothing is repeated from the name or title.

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?

For a 7-parameter search with no output schema, the description covers the two things structured fields cannot: matching semantics and the abbreviated return shape. Minor gaps remain — result ordering/relevance and whether paid-access items appear by default — but these are not blocking for correct invocation.

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, but the description adds real meaning for the required query parameter by specifying AND semantics across multiple fields — the schema only says "Words to look for." The other six parameters (kind, limit, topic, access, checked, runs_on) are left entirely to the schema, which is acceptable given its richness.

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 ("Search BotShelf Vampire items by words") and immediately defines the matching rule: every word must match title, description, where-it-runs, topic or keywords. It also distinguishes itself from the sibling get_item by declaring that it returns short cards, so an agent can tell the two apart without opening a schema.

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 routing guidance for the main decision point: use this tool for short cards, then call get_item for full text. It does not explicitly exclude or compare against list_items for browsing or state when a search is the wrong choice, so it stops short of full when/when-not coverage.

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.