Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

UK New Company Leads (Companies House)

find_uk_new_companies

Find newly incorporated UK companies by date, SIC code or industry keyword, location and company type, returning company numbers, names, addresses, SIC descriptions and directors from Companies House.

Instructions

Find newly incorporated UK companies from the official Companies House register, filtered by date, SIC code or industry keyword, location and company type. Returns company number, name, address, SIC descriptions and directors. Priced per company. Runs the Apify actor zrk1212/uk-new-company-leads on your Apify account.

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": "find_uk_new_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysBackNoCompanies incorporated in the last N days (default 7).
locationNoTown, city or county, e.g. 'Manchester'.
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
sicCodesNoSIC codes, e.g. ['62012'] for software development.
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
extraInputNoAny other input field of the Apify actor zrk1212/uk-new-company-leads, passed through as-is. See https://apify.com/zrk1212/uk-new-company-leads/input-schema
sicKeywordsNoIndustry keywords matched against SIC descriptions, e.g. ['restaurant'].
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
includeOfficersNoInclude directors and officers (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag openWorldHint and non-read-only behavior, but the description adds the crucial context that this spends real money ('Priced per company' and 'Runs the Apify actor ... on your Apify account'). That is exactly the kind of cost/execution disclosure annotations cannot carry. It does not cover timeout behavior or pagination, though the schema does.

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 sentences, front-loaded with purpose, then filters and outputs, then pricing and execution model. Every sentence carries distinct information and nothing is repeated from the schema.

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 correctly enumerates the returned fields, and it discloses cost and execution context. It leaves out pagination and timeout behavior, but those are covered in the parameter descriptions (maxItems, waitSecs). Slightly more could be said about result volume expectations, but it is close to complete.

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 every parameter is already documented with examples. The description only summarizes the filter categories (date, SIC code or industry keyword, location, company type), adding no syntax or constraint detail beyond the schema. Baseline 3 applies.

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 states a specific verb (Find), a tightly scoped resource (newly incorporated UK companies from the official Companies House register), the filters supported, and the fields returned. An agent can tell exactly what this tool produces without opening the schema, and it does not overlap with any listed sibling.

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 only implied by the tool's subject matter ('newly incorporated UK companies'). There is no explicit when-to-use or when-not-to-use guidance, no mention of what to do instead for older companies or non-UK entities, and no prerequisites stated beyond the actor reference.

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