Skip to main content
Glama

ESearchCy — Cyprus company search

Search Cyprus companies

search_companies
Read-only

Find Cyprus companies and partnerships registered with the Registrar of Companies, by registration number (e.g. "HE 123456", "ΗΕ 123456", "S 1817") or by the start of the registered name (e.g. "BANK OF CYPRUS"). Returns name, number, status, registration date and the company page link. Includes struck-off and dissolved companies.

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": {
      "query": "<query>"
    },
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRegistration number, or the beginning of the company name (Latin or Greek).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the useful disclosure that struck-off and dissolved companies are included, which prevents the agent from assuming an active-only registry. It says nothing about result caps, pagination, or matching behaviour beyond prefix, which matters for a search endpoint.

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 compact sentences: the first carries the search modes with examples, the second the return fields, the third a scoping caveat. Every sentence adds information and the most decision-relevant content (how to query) is front-loaded.

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?

For a one-parameter read-only lookup with no output schema, the description covers what to pass in, what comes back (name, number, status, registration date, page link), and the inclusion of dissolved entities. The remaining gap is result-set behaviour — how many matches are returned and whether results are truncated — which an agent would want before relying on it.

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% and the single parameter is already documented as a registration number or name beginning in Latin or Greek, so the baseline is 3. The description does add value with concrete number formats ('HE 123456', 'ΗΕ 123456', 'S 1817') that clarify the prefix conventions, but it does not explain number-vs-name disambiguation or partial-name edge cases.

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?

States a specific verb ('Find') and resource (Cyprus companies and partnerships registered with the Registrar of Companies), and names the two lookup modes — registration number or name prefix. It is clearly a search tool rather than a detail fetch, though it never names get_company as the follow-up for a single record, so sibling differentiation is implied rather than stated.

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?

Gives concrete invocation examples for both query modes ('HE 123456', 'ΗΕ 123456', 'S 1817', 'BANK OF CYPRUS'), which tells the agent exactly what shape of input to supply. It does not state when to prefer get_company over this tool or what to do when the search returns nothing, so there are no explicit exclusions or alternatives.

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