Skip to main content
Glama

Sisoco One

Search UK companies

sisoco_search_company
Read-onlyIdempotent

Searches the Companies House register (UK) by name or number and returns matching companies with number, status and address. Use it to find the company number to pass to sisoco_check_company or sisoco_ownership_chain. For French companies call sisoco_check_company with the name and country FR. Cost: 1 lookup (same as GET /v1/companies/uk/search).

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": {
      "q": "<q>"
    },
    "name": "sisoco_search_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCompany name or number
start_indexNoOffset of the first result
items_per_pageNoResults per page (1–100, default 20)

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the description's real contribution is the cost model: 1 lookup, equivalent to GET /v1/companies/uk/search. That billing/rate context is genuinely useful and not derivable from annotations or schema. It stops short of describing pagination behavior or result-size limits against the start_index/items_per_page params, which keeps it off a 5.

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 tight sentences: capability and return fields first, then the routing purpose, then the exception and the cost. Every sentence carries distinct information with no restated name or title, and no filler.

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?

An output schema exists and the description still summarizes the meaningful return fields (number, status, address), so nothing is missing there. With annotations covering safety and the schema covering all three params, the remaining gaps an agent could face — pagination semantics — are minor for a search tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds real value by clarifying that q accepts either a company name or a company number, which shapes how an agent fills the required field. It does not add anything beyond the schema for start_index or items_per_page, but that is acceptable given the schema fully documents them.

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?

States a specific verb (searches), specific resource (Companies House UK register), and the exact match fields (name or number), plus what comes back (number, status, address). It explicitly separates itself from siblings by naming sisoco_check_company and sisoco_ownership_chain as downstream consumers of the company number.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit use case (resolve a company number before calling the check/ownership tools) and an explicit exclusion — French companies should go to sisoco_check_company with country FR instead. This is exactly the when-to-use / when-not / alternative structure the top band requires.

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