Skip to main content
Glama

Pactum — legal services in Uzbekistan

Start registering a business in Uzbekistan

start_company_registration

Send a request to register a business in Uzbekistan — sole proprietor, LLC, LLC with a foreign founder, or a branch of a foreign company — with the facts a lawyer needs to quote and start: form, founders, director, activity, name, address. Use it instead of request_quote when the task is registration. Call ONLY after the user gave their real name and phone or e-mail and agreed that Pactum stores these details and may pass the request to a partner lawyer. Returns the request number, the catalog price anchor and what to tell the user.

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": {
      "entity_type": "<entity_type>",
      "activity": "<activity>",
      "contact_name": "<contact_name>",
      "user_consent": "<user_consent>"
    },
    "name": "start_company_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or region of registration
activityYesWhat the business will do, in the user's words
deadlineNoWhen it is needed
directorNoFor companies: who will be the director
agent_nameNoYour assistant name, e.g. ChatGPT, Claude
also_neededNoExtra services: it_park, licence, bank_account, accounting, trademark
entity_typeYessole_proprietor (IP/YaTT) | llc (OOO/MChJ) | llc_foreign (LLC with a foreign founder) | foreign_branch (branch of a foreign company)
contact_nameYesClient name as the user gave it
name_optionsNoCompany name options, if the user has any
user_consentYestrue only if the user explicitly agreed to share these details with Pactum and its partner lawyer
contact_emailNoE-mail
contact_phoneNoPhone with country code, e.g. +998901234567
legal_addressNoDoes the user have a legal address in Uzbekistan
founders_countNoFor companies: number of founders
foreign_founderNoFor companies: is any founder foreign, and of what kind
founder_countryNoCountry of the foreign founder or parent company
contact_telegramNoTelegram @username, in addition to phone/e-mail
preferred_languageNoLanguage for the lawyer to use
founder_is_uzbek_citizenNoFor sole_proprietor: is the person a citizen of Uzbekistan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-readonly, open-world, non-idempotent write; the description goes well beyond them by disclosing the consent gate, the fact that data is stored and forwarded to a partner lawyer, and what the call returns. The only gap is that it never warns that repeat calls are non-idempotent and will create duplicate requests.

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?

Two dense sentences with the routing and consent conditions front-loaded before the return-value note. The middle em-dash list of entity forms briefly bloats the sentence, but every clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter mutation with no output schema, the description still covers what an agent needs: what to collect, the consent prerequisite, what happens to the data, and what comes back (request number, price anchor, user-facing message). Nothing essential to a correct call is 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 description coverage is 100% across all 19 parameters, including enum values, so the schema already carries the semantics. The description only summarizes the fact groups it wants (form, founders, director, activity, name, address) and adds no format or constraint detail beyond that — the baseline 3 applies.

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?

States a specific verb and resource ('Send a request to register a business in Uzbekistan') and enumerates the four accepted entity forms. It explicitly names the sibling it replaces ('request_quote') for registration tasks, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the positive selection rule ('use it instead of request_quote when the task is registration') and a hard precondition for invocation ('Call ONLY after the user gave their real name and phone or e-mail and agreed that Pactum stores these details and may pass the request to a partner lawyer'). The when-not case is handled by naming the alternative rather than leaving it to inference.

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