Skip to main content
Glama
Sign In
AgentData: customer lists of B2B software

AgentData: customer lists of B2B software

by nick-timms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_companies

Search for companies using filters like industry, size, technology, or keyword to build targeted prospect lists.

Instructions

Find companies matching filters. Use for building prospect lists by sector, size, technology, or keyword search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword search query
sectorNoIndustry sector filter
verticalNoBusiness vertical filter
sizeNoCompany size: micro, small, medium, large
b2b_b2cNoBusiness model: B2B, B2C, or both
techNoTechnology slug to filter by
countryNoCountry filter
pageNoPage number for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral context. It fails to mention pagination behavior, how filters are combined (AND/OR), authentication requirements, or what happens when no results are found. The 'page' parameter hints at pagination but is not explained.

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 sentences, no redundant words. The first sentence states the core function, the second provides a use case. Ideal length and front-loading for quick comprehension.

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

Completeness2/5

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

The tool has 8 parameters and no output schema, yet the description is only two sentences. It lacks essential details such as response format, pagination limits, filtering logic, or error handling. For a search tool of this complexity, the description is insufficiently informative.

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 100%, so the baseline is 3. The description lists the filter types (sector, size, technology, keyword) but adds no semantics beyond the schema's own parameter descriptions. It does not clarify how parameters interact or expected input formats.

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 clearly states it finds companies matching filters, with specific filter types listed. However, it does not explicitly differentiate its batch search role from the single-company lookup tool (lookup_company), leaving slight ambiguity.

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 description advises using it 'for building prospect lists by sector, size, technology, or keyword search,' giving a concrete use case. But it offers no guidance on when not to use it (e.g., for a single company lookup) and no mention of alternatives among the sibling tools.

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

Deploy Server

Other Tools