Skip to main content
Glama

Venoh AI Visibility

Find buyer questions

find_buyer_questions
Read-onlyIdempotent

Lists the plain questions buyers ask AI assistants when looking for a provider in a category and city.

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": {
      "category": "<category>"
    },
    "name": "find_buyer_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoCity or country, for example Mumbai or India. Defaults to India.
categoryYesWhat the business sells, for example CA firm or CRM software

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds the meaningful trait that results are "plain questions" asked of AI assistants — natural-language queries rather than keywords — but says nothing about volume, whether results are generated or collected, or what the response shape looks like.

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 well-formed sentence with the resource and both scoping dimensions front-loaded and no redundant wording. It is efficient but arguably too thin given the unanswered behavioral questions.

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?

For a simple two-parameter read-only tool this is close to adequate, and no output schema exists so the description should hint at the return form — it only says "questions" without indicating a list of strings versus structured objects or any result count. An agent could call it correctly but cannot anticipate the output.

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 description coverage is 100%, so both parameters are already documented with examples and the India default. The description reinforces that category and city jointly scope the query but adds no syntax or format detail beyond the schema; baseline 3 applies.

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?

The description uses a specific verb ("Lists") with a clearly bounded resource ("plain questions buyers ask AI assistants") and scope ("in a category and city"). It is clearly distinguishable from check_ai_visibility and get_venoh_plans by resource, though it never explicitly contrasts with them.

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?

It states what the tool returns but gives no when-to-use guidance, no prerequisites, and no exclusions or alternatives. The agent must infer from the purpose alone whether to call this versus check_ai_visibility.

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