Skip to main content
Glama

ESearchCy — Cyprus company search

Cyprus company details

get_company
Read-only

Registry details of one Cyprus company or partnership: name, type, status and its date, registration date, registered office address, number and roles of current officers (no names), previous officers count, the date of the open data, and links to the company page and to order its documents.

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": {
      "number": "<number>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesRegistration number, e.g. "HE 123456" or "S 1817". A bare number means a company (HE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: it lists exactly what registry data is exposed, notes that officer names are withheld ('no names'), mentions a previous-officers count, and includes a date for the open data, which helps the agent judge freshness. It does not describe what happens when the number is unknown or invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single dense sentence that front-loads the resource and then enumerates the payload. Every clause maps to actual returned data, though the long comma-separated list is slightly harder to scan than a short structured breakdown would be.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly, including privacy limits on officer names and links to related actions. Gaps are minor: no error behavior for an unknown registration number and no note on how partnership records differ from company records.

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 description coverage is 100%: the schema already explains the registration number format ('HE 123456' or 'S 1817') and that a bare number means a company. The description's reference to 'company or partnership' aligns with that but adds no new syntax, validation, or formatting detail beyond the schema, so the baseline of 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 states a specific verb and resource: registry details of one Cyprus company or partnership, and it enumerates the fields returned (name, type, status, address, officer counts, links). An agent can tell this is a single-entity lookup, but the description does not explicitly contrast it with the sibling search_companies beyond the singular 'one company' framing.

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 implied by the combination of 'one Cyprus company' and the required registration number: use this to fetch details for a known entity. There is no explicit when-to-use versus search_companies or get_documents_and_prices, and no stated preconditions such as needing a valid registration number.

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