Skip to main content
Glama

search_buyer_answers

Read-onlyIdempotent

Keyword search over Deal OS's public short answers to buyers' due diligence questions (earnouts, SOC 2, QoE, data room, AI reliability). Ends with the source URL.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond them: the corpus is public short answers, matching is keyword-based rather than semantic, and each result ends with the source URL. It does not discuss result caps or ranking, which is the main remaining gap.

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?

Two compact sentences: the first front-loads what is searched and over what corpus, the second adds the one return-value detail worth flagging. No filler or restatement of the name.

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?

Low-complexity tool (one required parameter), annotations covering safety, and an output schema covering return shape. The description supplies corpus scope, matching method, and topical domain — everything needed 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 0% — the single 'query' parameter has only a generic title — so the description carries the burden. Calling it a 'keyword search' tells the agent to pass keywords rather than a full natural-language question, which is meaningful semantics for this parameter.

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 ('keyword search over Deal OS's public short answers to buyers' due diligence questions') and enumerates topical coverage (earnouts, SOC 2, QoE, data room, AI reliability). The 'search' verb cleanly separates it from the get_* siblings, though no sibling is named explicitly.

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?

Usage is implied by 'keyword search' over a defined corpus, so an agent can infer when to reach for it, but there is no explicit when-to-use versus when-to-use-a-sibling statement or any exclusion. No guidance on what to do if the query yields nothing.

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