Skip to main content
Glama

Search Rainbrand documentation

search_docs
Read-onlyIdempotent

Search public Rainbrand documentation for API integration and MCP usage. Returns matching content, page URLs, and metadata. Follow message_for_assistant to fetch relevant full pages as Markdown.

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_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesDescribe the Rainbrand integration question or topic you want documentation for. Exclude secrets and private customer data.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
queryYesSearch query after surrounding whitespace is removed.
resultsYesDocumentation matches in search-result order. Empty when the search succeeds but finds no matches.
message_for_assistantNoGuidance for fetching relevant full pages as Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add workflow context - and it does, stating what comes back (matching content, page URLs, metadata) and instructing the agent to follow message_for_assistant to fetch full pages as Markdown. That follow-up protocol is genuinely useful information not present in the annotations or schema. It does not mention result limits or ranking behavior.

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, each doing distinct work: purpose and scope first, then return contents, then the next-step instruction. No repetition and nothing that could be cut without losing information.

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 two-parameter search tool with full schema coverage and an output schema, this is nearly complete - purpose, scope, return shape, and a follow-up workflow are all stated. A brief note on result volume or how to refine a query would close the remaining gap.

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% and the schema already explains both parameters in detail, including the PII warning on query and the optional/analytics-only nature of llm_model. The description adds no parameter-level meaning beyond the schema, 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?

The description names a specific verb and resource - 'Search public Rainbrand documentation' - and scopes it to 'API integration and MCP usage'. That is enough to separate it from every listed sibling, none of which touch documentation, though it does not explicitly contrast with a nearby search-style tool like search_user_images.

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 context for use: questions about Rainbrand API integration and MCP usage, and the word 'public' implicitly sets the boundary that private/account data is out of scope. It stops short of explicit when-not guidance or naming an alternative tool for adjacent questions.

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.

Resources