Skip to main content
Glama

rr_search_knowledge

Read-onlyIdempotent

Search the ReplenishRadar knowledge base for product features, best practices, and inventory-management concepts that live seller data cannot answer.

Instructions

Search the ReplenishRadar knowledge base for product features, best practices, and inventory management concepts: the answers the seller's live data does not hold.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language search query
top_kNoNumber of results to return (default 5, max 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the domain-scoping insight about what the corpus contains; it says nothing about ranking, result shape, or whether results include source citations.

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?

One sentence, front-loaded with the verb and resource, and the qualifier clause carries real meaning about when to reach for it. Nothing redundant with the title or 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?

For a simple two-parameter read tool with full annotations and full schema coverage, the description covers purpose and domain well. The one remaining gap is the absence of an output schema combined with no hint about what a result looks like (snippets, docs, citations).

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 'query' and 'top_k' (including default 5 and max 10) fully documented in the schema itself. The description adds no query-syntax or phrasing guidance, so the baseline 3 applies.

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?

States a specific verb ('Search') and resource ('the ReplenishRadar knowledge base') plus the content types covered: product features, best practices, inventory management concepts. The trailing clause 'the answers the seller's live data does not hold' draws a boundary against the data-retrieval siblings, though no sibling is named explicitly.

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 a clear selection condition: use this when the seller's live data does not contain the answer, i.e. for conceptual/help content rather than live inventory numbers. It stops short of explicit exclusions or naming an alternative tool for data lookups, so the agent must infer the complement.

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