Skip to main content
Glama

Bulgaria company

run_bg_companies
Read-onlyIdempotent

Get one company from the Bulgaria registry (Commercial Register) by UIC (ЕИК) or registry link: name, status, first registration date, address and contacts, legal form, activity, capital and shares, representatives and board, procuracy, trade-undertaking transfers, mergers, predecessors/successors, liquidation, beneficial owners (NPLE), registrar instructions and court case files. 15 points 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": {
      "company": "<company>"
    },
    "name": "run_bg_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesUIC (ЕИК) or registry URL. e.g. 831902088

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the safety profile is handled. The description adds genuinely non-schema information: the credit cost ('15 points per returned record') and the full breadth of returned data, which is exactly what an agent needs for cost-aware planning. It omits failure behavior (invalid UIC, non-registry URLs).

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?

Front-loaded with the verb, source and identifier types before the long field enumeration, and the pricing note is isolated at the end. The middle field list is dense but every item is a real returned section, so it earns its space.

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 read-only single-record lookup with no output schema, the description enumerates the returned sections (registration data, officers, procuracy, mergers, beneficial owners, court files) well enough for an agent to judge suitability, and states the cost. Only error/not-found behavior and the search alternative are missing.

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 already documents 'UIC (ЕИК) or registry URL' with an example. The description restates the same two accepted formats without adding format rules, validation behavior, or what happens when a URL is not a Bulgarian registry link. Baseline 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?

States a specific verb and resource: 'Get one company from the Bulgaria registry (Commercial Register)', and 'one' distinguishes it from a listing/search operation. It never names run_bg_companies_search or run_bg_company_filings, so the differentiation is implied rather than explicit.

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?

'Get one company ... by UIC (ЕИК) or registry link' implies this is the single-record lookup versus the search sibling, but no when-to-use / when-not guidance is stated and no alternative is named. The accepted input formats are the only actionable guidance.

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