Skip to main content
Glama

Sisoco One

Check a company

sisoco_check_company
Read-onlyIdempotent

Start here. Resolves a UK company number, French SIREN, LEI, or a company name with country (GB or FR) to one company, and returns its identity, current signals (e.g. accounts overdue, insolvency notice, sanctions possible match) and events of the last 90 days, each with its official source URL. A name that matches several companies returns error ambiguous_match with ranked candidates; call again with a candidate's number. Facts from official registers, never a score or a verdict; sanctions results are possible matches that need the user's own review. Cost: 1 lookup from the monthly quota (same as GET /v1/check).

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": {
      "company": "<company>"
    },
    "name": "sisoco_check_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesRegistry number (e.g. 00445790, SIREN 552032534), LEI, or a company name
countryNoISO 3166-1 alpha-2 (GB, FR); needed for name searches

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, and the description adds substantially beyond them: quota cost ('1 lookup from the monthly quota'), the ambiguous_match error contract with ranked candidates, provenance ('official registers, never a score or a verdict'), and the 90-day event horizon. That is exactly the operational and epistemic context an agent needs before spending a quota unit.

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?

Front-loaded with 'Start here' followed by capability, return contents, ambiguity handling, interpretation caveat, and cost, in that order. Every sentence carries distinct information and none restates the tool name or title.

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?

For a two-parameter, read-only lookup with an output schema, the description covers the remaining gaps an agent needs: error behavior on ambiguity, quota cost, provenance and the limits of sanctions matching. Return shape is delegated correctly to the output schema rather than duplicated.

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 structured form, including that country is 'needed for name searches'. The description reinforces the accepted identifier types and country scope but adds no format or syntax detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ('Resolves a UK company number, French SIREN, LEI, or a company name with country ... to one company') and enumerates what comes back: identity, current signals, and 90 days of events with source URLs. The single-company resolution scope plus the ambiguous_match fallback distinguishes it from a browsing/search sibling without the agent needing to open any 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?

'Start here' gives an explicit entry-point recommendation, and the ambiguity path is spelled out ('call again with a candidate's number'). It also sets an expectation about interpretation ('sanctions results are possible matches that need the user's own review'). It stops short of naming a sibling to use instead when the agent wants a list of candidates rather than one resolution, so it falls just short of a 5.

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