Skip to main content
Glama

Search the StaffBots FAQ

faq_search
Read-onlyIdempotent

Search official StaffBots FAQ answers about plans, pricing, resellers, StaffBots OS, contact, and brand disambiguation versus StaffBot at staffbot.ai.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax answers to return (default 5).
queryYesA question or keywords to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety and determinism profile is covered. The description adds that answers are 'official' and scoped to the StaffBots brand, which is modestly useful context, but says nothing about result shape, ranking, or what happens when no FAQ matches.

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?

A single front-loaded sentence with no filler; the topic enumeration earns its place by conveying scope. The trailing brand-disambiguation clause is slightly awkward but still informative.

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, read-only, closed-world search tool with full schema coverage and no output schema, the definition covers purpose and scope adequately. Nothing essential to calling it correctly is missing.

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% — both 'query' and 'limit' (with default and max 10) are documented in the schema. The description adds no meaning beyond that, so the baseline of 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 ('official StaffBots FAQ answers') and enumerates the topical scope (plans, pricing, resellers, StaffBots OS, contact, brand disambiguation). This separates it from most siblings like get_plan or list_industries, though it never explicitly contrasts with search_docs, the closest overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The topic list implies when to reach for this tool (factual FAQ questions rather than structured plan data), but there is no explicit when-to-use or when-not-to-use statement, and no mention of when search_docs is the better choice.

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