Skip to main content
Glama
Ploid MCP

Ploid MCP

Official
by ploidcom

Find decision-makers

find_decision_makers

Build a verified list of likely buyers and influencers at a target company for a specific product, with count and title filters, and get a resumable run ID for status checks.

Instructions

Build a verified list of likely buyers and influencers at a company for a specific product. count must be 1 to 20; other values are rejected without starting a job. Returns a resumable run_id; use get_research_status for the list.

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": {
      "company": "<company>",
      "product": "<product>"
    },
    "name": "find_decision_makers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoPeople to find. Whole number from 1 to 20, default 5. Values outside this range are rejected without charge.
titlesNoJob titles to prioritize, up to 8 titles of 50 characters each.
companyYesThe company to search, up to 200 characters.
productYesThe product or service being sold, up to 300 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-destructive operation, but say nothing about job lifecycle or cost. The description supplies the important extras: invalid counts are rejected without starting a job (no charge incurred) and the call returns a resumable run_id rather than the results themselves. It doesn't say what 'verified' means or how long a run takes, which keeps it below a 5.

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?

Three short sentences, front-loaded with the purpose, then the constraint, then the return path. Minimal waste, though the count range sentence duplicates what the schema already states verbatim, which is the one redundant clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining the return value and does so by naming the run_id and the follow-up tool. For a four-parameter async research job that is close to complete; the missing piece is any indication of what the eventual list contains or how results are scoped to product.

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 all four parameters are already documented, including the 1-20 count range and the 8-title limit. The description only restates the count bound and leaves titles, company, and product meaning to the schema. Baseline 3 is correct since the schema does the heavy lifting.

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 gives a concrete verb and resource: build a verified list of likely buyers and influencers at a company, qualified by the product being sold. That is far more specific than 'find people', and the product-scoping constraint implicitly separates it from a generic people search. It stops short of naming the near-identical siblings (find_people, search_people), so an agent still has to infer which targeting mode to pick.

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?

It states the valid input envelope ('count must be 1 to 20; other values are rejected without starting a job') and routes the agent onward: 'use get_research_status for the list'. That is clear operational context for an asynchronous job. There is no explicit when-not-to-use or comparison against find_people/search_people, so selection between the similar siblings remains implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.