Skip to main content
Glama

search

Read-only

Search the user's ExpenseBot data — expenses, reports, and knowledge base. Returns matching items with id, title, and url. Use the returned id with the fetch tool to get full details. Powers Deep Research and Company Knowledge integrations. For filtered expense lists, totals or expenseIds to edit use search_expenses; for help articles use search_knowledge.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language search (e.g., 'Uber rides in March', 'Q1 client report', 'mileage Acme')

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 the safety profile is covered by structured data. The description adds value beyond that by disclosing the result shape and that this is a top-level entry point consumed by Deep Research and Company Knowledge integrations. It stops short of describing result caps or pagination, which is the only meaningful gap.

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?

Front-loaded and dense: purpose, return shape, follow-up tool, then sibling routing in three sentences. The one expendable clause is 'Powers Deep Research and Company Knowledge integrations,' which is contextual marketing rather than something that affects tool selection.

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 one-parameter read-only search tool, the description covers purpose, scope, return fields, the downstream fetch step, and disambiguation from both similarly named siblings. An output schema exists and is not redundantly explained, and annotations handle the safety contract.

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?

There is a single parameter with 100% schema description coverage, including natural-language examples, so the schema carries the semantic load. The description adds no syntax, ranking, or matching behavior beyond what the schema already states, which lands at the documented baseline of 3.

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 with scope: 'Search the user's ExpenseBot data — expenses, reports, and knowledge base.' It also declares the return shape (id, title, url), so an agent knows both what it searches and what it yields 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?

Explicitly routes to alternatives: search_expenses for filtered expense lists, totals, or expenseIds to edit, and search_knowledge for help articles. It also names the follow-up step ('Use the returned id with the `fetch` tool'), giving a complete search-then-fetch workflow rather than leaving the agent to infer it.

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.