Skip to main content
Glama

Pactum — legal services in Uzbekistan

Pactum company details

get_company_info
Read-only

Who Pactum is: legal entity and tax ID, office address, phone, e-mail, business hours, working languages, what it does and does not do, how prices are set, and contract/payment terms for foreign clients. Use it when the user asks who they would be dealing with or how to pay.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_company_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoResponse language: ru, uz or en (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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, so the safety profile is covered. The description adds that the content is static reference material about the firm (including what it does not do and how prices are set), but says nothing about freshness, caching, or response shape. Useful context, but modest beyond the annotations.

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, front-loaded with 'Who Pactum is:' followed by a compact enumeration, then a single usage sentence. The long field list is dense but every item conveys distinct retrievable content, so nothing is wasted.

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 simple, read-only, zero-required-parameter lookup with no output schema, the description is nearly sufficient: it tells the agent what topics the response covers and when to call it. Only the locale/default-language behavior is left unaddressed.

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?

There is a single optional locale parameter with 100% schema description coverage and an enum, so the schema fully documents it. The description does not mention locale or the default language, so it adds no meaning beyond the schema; 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?

The description names the resource (Pactum's company details) and enumerates the specific contents: legal entity/tax ID, address, phone, e-mail, hours, languages, scope of work, pricing policy, and contract/payment terms. That is far more specific than a tautology and clearly separates it from siblings like get_service or get_consultation_price, though it never names an alternative tool explicitly.

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?

It gives an explicit trigger: 'Use it when the user asks who they would be dealing with or how to pay.' That covers the main use cases well, but there is no when-not guidance or pointer to a sibling for adjacent questions (e.g. pricing figures vs. pricing policy).

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