Skip to main content
Glama

Pactum — legal services in Uzbekistan

Search Pactum (services, law articles, terms, state fees)

search
Read-only

One search across everything Pactum publishes about doing business and legal matters in Uzbekistan: legal services with price anchors, articles explaining Uzbek law, glossary definitions and the table of state fees. Returns ids, titles and URLs; pass an id to fetch for the full text.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query in English, Russian or Uzbek

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces the closed corpus ('everything Pactum publishes') and describes the two-step search-then-fetch workflow. However, it discloses nothing about result limits, ranking, pagination, or query-matching behavior, which are the operational traits an agent most needs for a search tool.

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, scope listed first, workflow second. No filler, no restatement of the title, and every clause carries actionable information.

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?

The tool is simple (one required param), annotations cover safety and openness, and an output schema covers return shape, so the description need only establish scope and the follow-up path — both present. The only meaningful omission is any hint about result volume or how to narrow an overly broad search.

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?

Only one parameter and schema coverage is 100%, so the schema fully documents the query string including its multilingual support and length bounds. The description adds no meaning beyond the schema about the query, which is acceptable given the high coverage but leaves nothing extra.

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 (search) and an explicitly enumerated resource scope: legal services with prices, law articles, glossary terms, and state fees. The phrase 'one search across everything Pactum publishes' clearly positions it as the federated search versus the narrower siblings like search_articles and search_services.

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

Usage Guidelines4/5

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

Gives a clear when-to-use signal (broad discovery across all published content) and an explicit next step: 'pass an id to fetch for the full text,' which routes the agent to the fetch sibling. It stops short of naming when to prefer search_articles or search_services instead, so the agent must infer that from scope language alone.

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