Skip to main content
Glama

regdata_cyprus_drcor

Search the official Cyprus DRCOR company registry by name or HE number to retrieve company identity, status, directors, secretary, and registered office. Even a verified 'not found' result provides a definitive answer.

Instructions

Cyprus DRCOR Company Registry Scraper. Look up Cyprus companies in the official DRCOR register by name or HE number. Returns company identity and status, directors and secretary, and registered office. A verified "not found in the register" is a real answer, not an error. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoLanguage for labels and values the register translates - organisation type, status and officer positions. Company names and addresses are returned exactly as the register holds them, which for older Cypriot files is Greek regardless of this setting.en
maxItemsNoOptional cap on billed dataset items returned.
maxResultsNoMaximum organisation records to export. A company that has traded under several names is listed once per former name in the register; those are merged into a single record here, with the former names kept on it, so you are never charged twice for the same company.
searchTypeNoHow the company name is matched. 'Starts with' is the register's default and the most reliable. 'Sounds like' uses the register's own phonetic index, which is narrow - it will not behave like a general fuzzy search.startsWith
companyNameNoCompany or organisation name to search for. Matching is controlled by the Search type below. Example: 'HELLENIC BANK', 'EUROBANK'. | Όνομα εταιρείας ή οργανισμού.
registrationNumbersNoOne or more Cyprus registration numbers, each looked up separately. Accepts any format: 'HE 6771', 'HE6771' or just '6771'. A bare number matches that number across EVERY organisation type (a limited company HE, a business name EE, an overseas company AE...), so include the letter prefix when you want just one type. | Αριθμοί εγγραφής, π.χ. 'ΗΕ 6771'.
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds behavioral context by stating that a 'not found in the register' is a valid response, not an error, and that advanced fields are accepted. However, it does not cover other important behaviors like rate limits, authentication, or idempotency.

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?

The description is highly concise: three sentences with no redundancy. It front-loads the purpose, then details returns, then adds a key behavioral note, and finally hints at advanced usage. Every sentence adds value.

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?

Given the tool has 6 parameters, no required fields, additional properties, and no output schema, the description is relatively complete. It explains the search scope, output fields, a critical behavioral nuance, and where to find extended parameters. Missing are examples or guidance on constructing queries, but overall adequate.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by mentioning that advanced fields beyond the schema are accepted and pointing to 'regdata_describe' for a list, but does not elaborate on the existing parameters beyond what the schema already provides.

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?

The description clearly states the tool scrapes the Cyprus DRCOR register, specifies it looks up companies by name or HE number, and lists what it returns (identity, status, directors, secretary, registered office). This distinguishes it from the many other country-specific registry siblings.

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?

The description implies use for Cyprus companies through the name and context, but does not explicitly mention when to use this tool versus alternatives like other country registries or when not to use it. It provides no guidance on exclusions or alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server