Skip to main content
Glama

Pactum — legal services in Uzbekistan

Add details to a request

add_request_details

Pass new facts from the user to the lawyer handling an existing request: a changed deadline, extra circumstances, a list of documents, a preferred call time. Needs the request number and the phone or e-mail the request was sent with. Does not create a new request. For a closed request send a new one instead.

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": {
      "request_number": "<request_number>",
      "contact": "<contact>",
      "details": "<details>"
    },
    "name": "add_request_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesThe phone (with country code) or e-mail given in that request
detailsYesWhat to add, in the user's words
agent_nameNoYour assistant name, e.g. ChatGPT, Claude
request_numberYesRequest number returned when it was sent

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 this as a non-readonly, non-destructive, non-idempotent, open-world mutation, and the description adds real context on top: it appends to an existing request rather than creating one, it requires identity corroboration via the contact used originally, and closed requests are rejected. What it does not disclose is what happens after submission (does the lawyer respond, is a confirmation returned?) or that repeated calls will stack duplicate facts given idempotentHint=false.

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?

Three short sentences: purpose, required inputs, then exclusions. The most decision-relevant constraint ('Does not create a new request') is placed before the edge case, and no sentence restates the title.

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 append tool with no output schema, the definition covers what it does, what it needs, and when it refuses. The only real gap for a mutating, open-world call is the lack of any statement about the outcome of a successful submission or duplicate-submission behavior.

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%, so all four parameters are already documented, including that contact must be the phone or e-mail originally given. The description reinforces that identity link and frames 'details' as the user's own words, but adds little syntax or format meaning beyond the schema, so 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 ('Pass new facts from the user to the lawyer handling an existing request') and follows with concrete examples of what counts as a fact (deadline change, extra circumstances, documents, call time). It also draws the boundary against the obvious confusion case ('Does not create a new request'), so an agent can distinguish it from the send-a-request tools.

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 clear positive guidance (existing request that needs updating) and an explicit negative case ('Does not create a new request. For a closed request send a new one instead'). It stops short of naming the sibling tool to use instead, leaving the agent to infer which of the sibling tools sends a new request.

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