Skip to main content
Glama

ADS Beast

client_memory_search

Read-only

Search the facts, decisions, preferences and brand notes ADS Beast has stored about clients.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, in plain words.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description usefully adds what corpus is being searched (client facts, decisions, preferences, brand notes), but says nothing about whether results are scoped or ranked, or whether omitting client_id searches across all clients.

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?

A single sentence with the verb front-loaded and zero filler; the enumerated content types are the substance rather than padding.

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 no output schema and only two parameters, the description is serviceable but leaves the client_id scoping behavior undefined and gives no guidance on result interpretation. Adequate as a minimum-viable definition, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: query is documented but client_id is not. The description says nothing about client_id's role, so an agent cannot tell whether it narrows the search to one client or is merely a hint, which is exactly the gap the description should have closed.

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?

Uses a specific verb ("Search") against a well-enumerated resource ("facts, decisions, preferences and brand notes"), which lets an agent distinguish it semantically from generic searches. It does not, however, contrast itself with near-neighbors like client_history_search or client_market_intel_search, so the boundary must be inferred.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this tool, when not to, or which sibling to prefer for adjacent needs (history vs. market intel vs. stored memory). The only guidance is implicit in the enumerated content types.

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.