Skip to main content
Glama

Pactum — legal services in Uzbekistan

Legal term under Uzbek law

lookup_term
Read-only

Definition of a legal or business term as Uzbek law defines it (e.g. MChJ/LLC, charter fund, beneficial owner, apostille, outstaffing, affiliated person), with the article of the act and a page URL to cite. Available in Russian and Uzbek; for other languages the Russian text is returned.

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": {
      "term": "<term>"
    },
    "name": "lookup_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe term or abbreviation, e.g. "уставный фонд", "MChJ", "апостиль"
localeNoResponse language: ru, uz or en (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 genuinely useful behavior beyond that: each result carries the article of the act and a citable page URL, and it discloses the language fallback rule (only ru/uz supported; other languages get the Russian text). It does not say what happens when a term is not found, but the added context is substantial.

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?

Two sentences, both front-loaded: the first defines the resource, the return payload and examples; the second covers the language constraint. No filler or redundant restatement of the tool name.

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, the description correctly takes on the burden of describing return values (definition, act article, page URL) and the locale fallback. It is nearly complete for a simple two-parameter lookup; only the not-found / partial-match behavior is left unspecified.

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 earns more by clarifying a real ambiguity: the locale enum accepts "en" while the description states that non-ru/uz languages return the Russian text, resolving the mismatch between the enum label and actual behavior. The term parameter's meaning is already well documented in the schema.

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 states a specific verb and resource ("Definition of a legal or business term as Uzbek law defines it") and anchors it with concrete examples (MChJ/LLC, charter fund, beneficial owner, apostille, outstaffing, affiliated person). This makes it clearly distinguishable from siblings like get_article or search_articles, which operate on whole acts rather than single terms.

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 examples and the term-lookup framing, but there is no explicit when-to-use or when-not guidance and no named alternative (e.g. "use search_articles if you don't know the exact term"). The language note is behavioral rather than routing 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