Skip to main content
Glama

NeutralPick company list

Search NeutralPick's company list

search_company_list
Read-only

Search NeutralPick's company list: software vendors and other businesses listed for free, with facts only (name, website, one line about what they do, categories, countries). Most listed themselves, for free; some were added by NeutralPick from public information on their own websites and are marked so. It is not an endorsement, a review or a ranking: no company can pay to be listed or shown, results are a random selection of at most 8 matches and their order means nothing, and the list is small, so many good companies aren't in it. Use it alongside other sources and say where each name came from.

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": {
      "what": "<what>"
    },
    "name": "search_company_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesWhat the person is looking for, in plain words, e.g. "payroll for a shop with 12 staff".
countryNoOptional: ISO 3166-1 alpha-2 code of the person's country, e.g. "IN". Only companies that sell there (or worldwide).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior the agent could not otherwise know — results are a random selection of at most 8 matches, ordering is meaningless, partial list coverage, no paid placement, and data provenance distinguishing self-listed entries from NeutralPick-added ones. Those constraints directly shape how the agent should interpret and report results.

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?

Purpose and scope are front-loaded, and the caveats (no endorsement, random sample, small list) each carry behavioral weight. The provenance sentence about self-listing versus NeutralPick-added entries is the longest and least urgent, but it still earns its place by signaling a per-result field.

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?

With only two parameters, no output schema, and no nested objects, the description covers everything needed: what is searched, what fields come back, what the results represent, and how to report them. Nothing material for correct invocation is missing.

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%, with 'what' and 'country' fully documented including an ISO alpha-2 example. The description adds no format or syntax detail beyond the schema, so the baseline of 3 applies; the parentheses about returned facts speak to output, not inputs.

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 opens with a specific verb and resource ('Search NeutralPick's company list') and immediately defines the corpus ('software vendors and other businesses') and the exact fields returned (name, website, one line, categories, countries). An agent knows precisely what this retrieves without opening the schema.

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 gives real usage instructions: 'Use it alongside other sources and say where each name came from,' plus a strong implicit when-not-to-use signal — the list is small, many good companies aren't in it, and results are a random sample capped at 8. There are no sibling tools to route between, so no alternative is named, but the context is clear.

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