Skip to main content
Glama

growthintel-mcp

Search Leads By Natural Language Tool

search-leads-by-natural-language-tool
Read-onlyIdempotent

Searches the authenticated tenant's leads using a free-text natural language query (Turkish or English), e.g. "qualified leads from web forms with high intent". The query is parsed into a constrained filter whitelist by an LLM — it can never generate arbitrary database queries. Returns the same anonymized scoring data as search-leads-tool (no name, email, phone, or company), plus which filters were inferred from the query.

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-leads-by-natural-language-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of leads to return.
queryYesFree-text natural language description of the leads to find.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses important behavior: an LLM parses the query into a constrained filter whitelist and cannot generate arbitrary database queries. It also specifies the return shape, including anonymized scoring data with no name, email, phone, or company, plus inferred filters.

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?

The description is three tightly written sentences that front-load the purpose, then explain the parsing constraint and return content. Every sentence adds useful information with no repetition or filler.

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 natural-language search tool with no output schema, the description covers the essential context: input language, LLM-imposed filter constraints, anonymization of returned data, and the extra inferred-filter output. No critical behavioral gap remains for an agent to call it correctly.

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 documents both parameters. The description still adds useful meaning for query by naming supported languages, giving an example, and explaining that it is parsed into a constrained filter whitelist; limit receives no additional explanation.

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 states a specific verb and resource: searching the authenticated tenant's leads via a free-text natural language query. It also distinguishes itself from the structured sibling search-leads-tool by explaining that results include inferred filters, so an agent can tell the two tools apart without opening schemas.

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

Usage Guidelines4/5

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

The description makes clear that this tool is for free-text natural language queries in Turkish or English, with an example. It does not explicitly say when to choose the structured search-leads-tool instead, so the routing guidance is clear but not complete.

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.

Resources