Skip to main content
Glama

ADS Beast

client_history_search

Read-only

Full-text search over a client's earlier reports, audits and analyses.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records.
queryYesSearch text.
client_idNo
report_typeNoaudit, monthly, jarvis_chat or all.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the scope of the corpus being searched; it says nothing about ranking, matching behaviour, or what happens to scope when no client is supplied.

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 wasted words; the resource and scope arrive immediately. It is efficient but so terse that it omits the qualification details the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four parameters, no output schema and only one sentence, the definition is thin: it does not explain result ordering, whether a missing client_id searches across all clients, or how full-text matching behaves. Adequate to attempt a call, but not complete for a search tool with an optional scoping parameter.

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 75%, so the schema largely documents query, limit and report_type itself. The description adds a weak signal that report_type maps to "reports, audits and analyses", but it never clarifies that client_id is optional or what the search scope becomes when client_id is omitted — the most consequential ambiguity in the schema.

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 and resource: full-text search over a client's earlier reports, audits and analyses. It is clear what the tool retrieves, but it offers no differentiation from near-neighbours such as client_memory_search or campaign_search, leaving an agent to infer which corpus each covers.

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 phrase "earlier reports, audits and analyses" implies the intended context, but there is no explicit when-to-use guidance, no statement of when a sibling search tool is preferable, and no prerequisites. Usage is inferable rather than stated.

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.