Skip to main content
Glama
Parsa-29
by Parsa-29

save_waybill

Destructive

Create or update a Georgian waybill (ზედნადები) by submitting structured data including buyer, driver, transport, and goods details. Builds the full XML for tax compliance.

Instructions

Create or update a waybill (ზედნადების შექმნა/რედაქტირება). Builds the full WAYBILL XML from structured input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoWaybill ID, 0 or omit for new
typeYesWaybill type (1=inner, 2=transportation, 3=without transport, 4=distribution, 5=return, 6=sub-waybill)
is_medNo0=normal, 1=medicine
par_idNoParent waybill ID (for sub-waybills)
statusYesStatus: 0=saved, 1=active, 2=closed
commentNoComment
categoryNoCategory: 0=normal, 1=wood
trans_idYesTransport type ID from get_trans_types
buyer_tinYesBuyer TIN (taxpayer identification number)
trans_txtNoTransport type text (when trans_id=other)
begin_dateYesTransport start date (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss)
buyer_nameYesBuyer name
car_numberNoVehicle plate number
driver_tinYesDriver personal number
goods_listYesGoods/items list (at least one item)
driver_nameYesDriver full name
end_addressYesUnloading/end address
seler_un_idYesSeller unique ID (from get_un_id)
sub_waybillsNoSub-waybill references
delivery_dateNoDelivery date (YYYY-MM-DD)
receiver_infoNoReceiver info
start_addressYesLoading/start address
chek_buyer_tinNo1=Georgian TIN, 0=foreign ID
reception_infoNoReception info
waybill_numberNoWaybill number (assigned on activation)
wood_docs_listNoWood documents (for category=1)
chek_driver_tinNo1=Georgian TIN, 0=foreign ID
tran_cost_payerNoTransport cost payer: 1=buyer, 2=seller, 3=other
transport_coastNoTransport cost
Behavior3/5

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

Annotations already indicate destructiveHint=true. The description confirms modification ('Create or update') and adds that it builds XML, but does not disclose additional behavioral traits like required permissions, idempotency, or side effects. Acceptable but minimal added value.

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?

The description is concise (two sentences) with no wasted words. However, it lacks structural elements like a summary of required fields or usage context, which could improve clarity.

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

Completeness2/5

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

Given the tool's complexity (29 parameters, 12 required, no output schema), the description is too sparse. It does not mention return values, error handling, or prerequisites, leaving significant gaps for the agent.

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 the schema already documents all 29 parameters. The description adds no extra meaning beyond stating that the tool builds XML. Baseline 3 is appropriate.

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 clearly states the action ('Create or update a waybill') and the resource, including a foreign language equivalent, making it specific. It distinguishes from sibling tools like get_waybill or del_waybill by focusing on the create/update action.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., close_waybill, send_waybill) or when to create vs update. No usage context is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Parsa-29/rs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server