Skip to main content
Glama

run_sk_companies_search

Search the Slovakia Commercial Register by business name prefix to find matching companies and retrieve links to their registry extracts.

Instructions

Search the Slovakia Commercial Register (Obchodný register SR) by the beginning of the business name: name and link to the registry extract. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_sk_companies_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesCompany name. e.g. slovnaft
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior beyond the schema: prefix matching and a per-record cost ('1 point per returned record'), plus what is returned. However, it omits auth requirements, rate limits, pagination behavior, and error handling.

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?

A single front-loaded sentence that covers the register, the match rule, the return contents, and the cost with no filler. Every clause earns its place.

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 output schema and no annotations, the description adequately conveys what the tool returns and how it matches. It stops short of describing pagination interaction between start_page/max_items, but for a simple search tool the essentials are present.

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?

Schema coverage is 100%, so the baseline is 3, but the description meaningfully clarifies that keyword is a prefix ('beginning of the business name') match rather than an arbitrary substring — an operational detail the schema's 'Company name. e.g. slovnaft' does not convey. The other two params (max_items, start_page) are self-documenting in the schema.

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+resource (search the Slovakia Commercial Register) plus the matching scope (beginning of the business name) and output (name + link to registry extract). Clear and unambiguous, but it never names or contrasts with the sibling run_sk_companies, leaving an agent to infer the search-vs-detail distinction.

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 phrase 'by the beginning of the business name', which tells the agent how the query is matched. There is no explicit when-to-use/when-not guidance and no alternative tool (e.g. run_sk_companies) is offered for looking up a known company.

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

Deploy Server

Other Tools