Skip to main content
Glama

ESearchCy — Cyprus company search

Documents and prices

get_documents_and_prices
Read-only

What ESearchCy can order from the Cyprus Registrar of Companies — the complete company file (every scanned document as PDF) and official certificates (incorporation, shareholders, directors and secretary, registered office, good standing, share capital, no winding-up, memorandum and articles) — with prices, delivery times and how to order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_documents_and_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 real content context by disclosing the scope (full PDF company file plus eight named certificate types) and that prices, delivery times and ordering steps are included. It does not explicitly say it merely returns information rather than placing orders, which would have removed residual ambiguity.

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?

A single sentence with the core purpose front-loaded and the document inventory in an em-dash parenthetical. The eight-item certificate enumeration is dense but earns its place by telling the agent exactly what is purchasable.

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?

With no parameters and no output schema, the description carries the descriptive load and does so adequately: it names the document types and states that prices, delivery times and ordering instructions are returned. A brief note on the shape of the response (e.g. a per-item list) would make it fully self-sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; it does not mislead about inputs, and the absence of arguments is consistent with a catalog-listing operation.

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 names a specific resource — the catalog of orderable documents and official certificates from the Cyprus Registrar of Companies — and enumerates the certificate types, so an agent knows exactly what comes back. It stops short of distinguishing itself from the sibling retrieval tools (get_company, search_companies), which fetch company data rather than a product/price list.

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 only implied: an agent can infer this is the tool to call when it needs to know what can be ordered, at what price and how fast. There is no explicit statement of when to prefer this over get_company or search_companies, and no exclusions or prerequisites.

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