Skip to main content
Glama

Search the PokeLances help docs

search_help
Read-onlyIdempotent

Search PokeLances help docs on payments, shipping, buying, products, and stores to find passages answering a buyer's or seller's question, with each answer cited to its source.

Instructions

Search PokeLances' help docs (payments, shipping, ways to buy, products, stores) for passages that answer a buyer's or seller's question. Answer ONLY with what the passages say and cite each one by its source. Each passage has its cosine similarity to the question; passages are always returned, so check that they actually answer it. If they don't, say you don't have that information instead of guessing.

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": {
      "question": "<question>"
    },
    "name": "search_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoPassages to return, default 3
questionYesThe user's question, in their own words

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses a non-obvious and decision-critical behavior: passages are always returned regardless of relevance, and each carries a cosine similarity score to the question, so the agent must verify the passages genuinely answer it. With no output schema, this is the only source of return-shape information, and it also implies a source field by instructing citation.

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 sentences, front-loaded with what the tool searches, then how to answer, then the relevance caveat. No redundancy and no filler; each sentence contributes a distinct instruction the agent needs.

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?

For a two-parameter retrieval tool with no output schema, the description covers what is retrieved, that results always come back with similarity scores, and how to ground and cite an answer. The remaining detail (default count of 3, max 5) is fully handled by the input schema.

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 both `question` and `k` documented in the schema itself, so the description is not required to explain them. It adds no syntax or format guidance for either parameter (e.g., how to phrase a question or when to raise `k`), leaving the schema to do all the work — the baseline 3 case.

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 — searching PokeLances' help docs — and scopes the covered topics (payments, shipping, ways to buy, products, stores) plus the audience (buyer or seller questions). That resource framing is enough to separate it from search_cards and search_store, which target catalog data rather than documentation.

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?

Gives clear conditions for use (a buyer's or seller's question about the listed help topics) and an explicit fallback: if the returned passages don't actually answer the question, state that the information isn't available rather than guessing. It never names a sibling tool as the alternative, so routing between help-doc search and card/store search is left implicit.

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