Skip to main content
Glama

search_knowledge

Read-only

Search ExpenseBot's complete product and help knowledge base. Use this before guessing when the user asks how a feature works, what ExpenseBot supports, or needs setup, billing, Gmail, scan, report, workflow, or troubleshooting instructions. Set fullAnswer:true on the first call when the user asks for complete, detailed, or step-by-step instructions. Use the default excerpt mode for discovery and quick answers; if an excerpt is truncated, call again with fullAnswer:true before presenting complete instructions. Each result has a stable id.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of ranked matching articles to return (1-10).
queryYesSearch terms
fullAnswerNoTrue on the first call for complete or step-by-step instructions.

Output Schema

NameRequiredDescriptionDefault
resultsYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / results / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / results / items / properties
      Removed value: -{
      -  "answer": {
      -    "type": "string"
      -  },
      -  "audience": {
      -    "type": "string"
      -  },
      -  "id": {
      -    "type": "string"
      -  },
      -  "note": {
      -    "type": "string"
      -  },
      -  "question": {
      -    "type": "string"
      -  },
      -  "relevance": {
      -    "type": "number"
      -  },
      -  "truncated": {
      -    "type": "boolean"
      -  },
      -  "type": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / results / items / required
      Removed value: -[
      -  "id",
      -  "question",
      -  "answer"
      -]
  2. Changed3 schema fields changed
    • changedInput schema / properties / fullAnswer / description
      Previous value: -"Set true on the first call for complete, detailed, or step-by-step instructions. Leave false for discovery or quick-answer excerpts."New value: +"True on the first call for complete or step-by-step instructions."
    • addedOutput schema / properties / results / items / properties / audience
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / note
      Added value: +{
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / fullAnswer / description
      Previous value: -"Set true to return complete article answers instead of short excerpts."New value: +"Set true on the first call for complete, detailed, or step-by-step instructions. Leave false for discovery or quick-answer excerpts."
  4. Changed8 schema fields changed
    • removedOutput schema / description
      Removed value: -"Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple."
    • removedOutput schema / properties / data
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
      -  "type": "object"
      -}
    • removedOutput schema / properties / error
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Present only when success === false.",
      -  "properties": {
      -    "code": {
      -      "type": "string"
      -    },
      -    "hint": {
      -      "type": "string"
      -    },
      -    "message": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / properties / message
      Removed value: -{
      -  "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / results
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "answer": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "question": {
      +        "type": "string"
      +      },
      +      "relevance": {
      +        "type": "number"
      +      },
      +      "truncated": {
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "question",
      +      "answer"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / sampleMeta
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
      -  "properties": {
      -    "isTruncated": {
      -      "type": "boolean"
      -    },
      -    "sampleCount": {
      -      "type": "integer"
      -    },
      -    "totalCount": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / properties / success / description
      Removed value: -"False on tool errors; check before reading `data`."
    • addedOutput schema / required
      Added value: +[
      +  "success",
      +  "results"
      +]
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior beyond that: results are ranked, excerpts can be truncated, and each result carries a stable id for follow-up. It does not mention rate limits or result ordering details, keeping it just short of a 5.

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?

Three sentences, front-loaded with purpose then decision rules, with no filler. There is mild redundancy between the initial fullAnswer instruction and the later truncation re-call sentence, which keeps it from a perfect score.

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?

An output schema exists, so return values need not be described, and the description still notes the stable id. For a read-only, three-parameter search tool, everything an agent needs to call it correctly and interpret truncation is present.

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 schema already defines all three parameters, which sets a baseline of 3. The description adds real usage semantics for fullAnswer — set it on the first call for detailed instructions, and re-call with it after a truncated excerpt — guidance the schema's one-line hint does not fully convey.

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?

The description opens with a specific verb and resource: 'Search ExpenseBot's complete product and help knowledge base.' The domain (product/help documentation) clearly separates it from expense-data siblings like search_expenses or get_pnl, so an agent can pick it without opening the schema.

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

Usage Guidelines5/5

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

It states explicitly when to reach for it ('before guessing when the user asks how a feature works... setup, billing, Gmail, scan, report, workflow, or troubleshooting') and gives mode-selection rules: fullAnswer:true for complete/step-by-step requests, default excerpt mode for discovery, and a re-call with fullAnswer when an excerpt is truncated.

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.