Zooq

search_companies

Read-onlyIdempotent

Search organizations by name or website with firmographic filters. Cursor-paginated. (Costs 10 Zooq credits.)

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

Name	Required	Description
`name`	No	Company name (min 3 chars). Provide name OR website.
`limit`	No	Results per page, 1-50 (default 20).
`cursor`	No	Opaque pagination cursor; omit for the first page.
`founded`	No	Founded year.
`hq_city`	No	HQ city filter.
`website`	No	Company website (min 3 chars). Provide name OR website.
`industries`	No	Industry name(s) — pass plain strings, comma-separated.
`industries_v2`	No	Industry v2 taxonomy name(s), comma-separated.
`hq_country_code`	No	HQ ISO country code.
`staff_count_max`	No	Maximum employee count.
`staff_count_min`	No	Minimum employee count.
`follower_count_max`	No	Maximum follower count.
`follower_count_min`	No	Minimum follower count.

Output Schema

Name	Required	Description	Default
`items`	No	Array in the example

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structural schema derived from a live example — field names and nesting only, no type constraints: fields may be absent, null, or a different primitive than the example, and new fields may appear. The text content block carries the same JSON.",
+  "properties": {
+    "items": {
+      "description": "Array in the example",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "follower_count": {
+            "description": "Example value was a number"
+          },
+          "headcount": {
+            "description": "Example value was a number"
+          },
+          "headcount_range": {
+            "description": "Example value was a string"
+          },
+          "hq_city": {
+            "description": "Example value was a string"
+          },
+          "hq_country_code": {
+            "description": "Example value was a string"
+          },
+          "id": {
+            "description": "Example value was a string"
+          },
+          "industries": {
+            "description": "Array in the example",
+            "items": {
+              "description": "Example value was a string"
+            }
+          },
+          "industries_v2": {
+            "description": "Array in the example",
+            "items": {
+              "description": "Example value was a string"
+            }
+          },
+          "name": {
+            "description": "Example value was a string"
+          },
+          "slug": {
+            "description": "Example value was a string"
+          },
+          "url": {
+            "description": "Example value was a string"
+          }
+        }
+      }
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false). The description adds useful non-annotation-specific behavior: cursor pagination and a credit cost of 10, which helps the agent anticipate side effects and usage cost.

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?

Three short sentences each earn their place: purpose, pagination behavior, and cost. The main action and scope are front-loaded, with no filler or repetition of schema details.

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?

Given a fully documented 13-parameter schema and an output schema, the description supplies the key invocation-level facts: search action, pagination, and credit cost. The main gap is the missing dataset-vs-live distinction relative to search_companies_live, but that is more a tool-selection concern than an invocation gap.

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 the baseline of 3 applies. The description only summarizes the parameters as 'name or website with firmographic filters' without adding detail beyond the schema. It does not need to compensate for gaps, and it doesn't.

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 ('Search') and resource ('organizations') and names the scope: by name or website with firmographic filters. It does not explicitly differentiate from closely related siblings like search_companies_live, so it misses the final distinction point for a 5.

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?

The description provides no when-to-use or when-not-to-use guidance and names no alternatives. Given overlapping siblings such as search_companies_live, companies_name_lookup, and companies_universal_name_to_id, an agent gets no help choosing among search entry points.

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

All Zooq tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?