Skip to main content
Glama

ADS Beast

client_market_intel_search

Read-only

Semantic search over a client's indexed market data: its site, competitor profiles and the market report.

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": {
      "client_id": "<client_id>",
      "query": "<query>"
    },
    "name": "client_market_intel_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text.
top_kNoNumber of results, 5 by default.
client_idYes

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 safety is covered. The description adds genuine value by disclosing that retrieval is semantic and scoped to three specific corpora, but it says nothing about whether an index must exist first, how results are ranked, or data freshness.

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 a compact colon-delimited corpus list, no filler. The only minor weakness is that the corpus list is dense and could be split for readability, but nothing is wasted.

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 three parameters, no output schema, and annotations covering the safety profile, the definition covers the essentials for invocation. It falls short on operational context an agent would want: whether an index is required, how many results are meaningfully retrievable, and what form results take.

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 67%: query and top_k are self-documented, but client_id has no description in the schema. The description's possessive framing ('a client's indexed market data') implicitly identifies client_id as the tenant scope, which is a modest addition over 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 ('Semantic search') and a specific resource ('a client's indexed market data'), then enumerates the corpora covered: site, competitor profiles, and market report. This is clearly distinct from analysis/simulation siblings, though it does not name competitor_search_intel or clarify how it differs from that near-neighbor.

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 'semantic search over indexed market data' implies usage (lookup rather than analysis), but there is no explicit when-to-use, when-not-to-use, or named alternative. Given numerous overlapping siblings such as competitor_search_intel and client_history_search, the agent must infer selection criteria itself.

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.