Skip to main content
Glama

count_companies_live_now

Read-only

Count live UK companies by SIC code and area to assess market density, with totals split by registration before 2021 and since.

Instructions

How crowded is it? Count companies (private limited, PLC and LLP) with these primary SIC codes that are live (not dissolved) in the snapshot, whatever year they were registered. Live includes companies that don't trade. Rows split it into those registered before 2021 and since. Area answers leave out formation-agent postcodes.

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": {
      "sic_codes": "<sic_codes>",
      "area": "<area>"
    },
    "name": "count_companies_live_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes'UK', a region or nation, or a council area code from find_area
sic_codesYesSIC codes from find_sic: 5 digits, a 2-4 digit group such as '812' for all of it, or a ready-made bundle id such as 'ai-and-data' (approximate). Choose codes for the activity asked about, e.g. cleaning: ['812']; digital and tech: ['62011', '62012', '62020', '62090', '63110', '63120', '58290']; every industry: ['all']. The choice can change the answer, so say which codes you used.

Output Schema

NameRequiredDescriptionDefault
rowsYes
answerYesThe summary plus both must-quote caveats, ready to pass on as one text.
caveatsYesThe first two are must-quote: include them in any answer.
summaryYesQuote this sentence word for word.
excludedYes
snapshot_dateYes
snapshot_sha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this as a safe read of a closed dataset, so the bar is lower. The description still adds real behavioral context: the snapshot nature, that live includes non-trading companies, that results are split into pre-2021 and since, and that formation-agent postcodes are excluded from area answers. That is meaningful methodology an agent would otherwise get wrong.

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?

Four tight sentences, front-loaded with the question it answers, then scope, then the live definition, then the caveat. There is little waste, although the row-split sentence partly duplicates what the output schema already conveys.

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 an output schema present, the description need not explain return values, and the key semantic risks (what 'live' means, registration-year split, formation-agent postcodes) are covered. The remaining gap is routing guidance against the many sibling counting and comparison tools.

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 both parameters are already documented in detail, including SIC code formats and bundles. The description only restates that codes must be primary SIC codes and that area responses exclude formation-agent postcodes; it adds no new parameter mechanics, so baseline 3 applies.

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 specific verb and resource: count companies (private limited, PLC, LLP) with given primary SIC codes that are live, in a named area. It also defines 'live' (not dissolved, even if not trading) and the year split, so an agent can tell this is a point-in-time count rather than a time-series or ranking. It does not name or differentiate from siblings such as count_incorporations_still_live, which keeps it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'How crowded is it?' frames the intended question, and the note about formation-agent postcodes explains a scope quirk. But there is no explicit when-to-use/when-not guidance and no pointer to alternatives like count_incorporations_still_live or compare_two_areas for the same SIC codes, so the choice is only implied.

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