Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_create_service

Create service records in POHODA accounting software by specifying date, description, partner name, and notes for maintenance tracking.

Instructions

Create a service record in POHODA

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesService date
textNoDescription
partnerNameNo
noteNo

Implementation Reference

  • The `pohoda_create_service` tool is defined here using the `server.tool` method, with input validation via `zod` and the handler logic that constructs the XML import request using `buildImportDoc` and submits it via `client.sendXml`.
    server.tool(
      "pohoda_create_service",
      "Create a service record in POHODA",
      {
        date: z.string().describe("Service date"),
        text: z.string().optional().describe("Description"),
        partnerName: z.string().optional(),
        note: z.string().optional(),
      },
      async (params) => {
        try {
          const xml = buildImportDoc({ ico: client.ico }, (item) => {
            const doc = item.ele(NS.ser, "ser:service").att("version", "2.0");
            const hdr = doc.ele(NS.ser, "ser:serviceHeader");
            hdr.ele(NS.ser, "ser:date").txt(toIsoDate(params.date));
            if (params.text) hdr.ele(NS.ser, "ser:text").txt(params.text);
            if (params.partnerName) {
              const pi = hdr.ele(NS.ser, "ser:partnerIdentity");
              pi.ele(NS.typ, "typ:address").ele(NS.typ, "typ:name").txt(params.partnerName);
            }
            if (params.note) hdr.ele(NS.ser, "ser:note").txt(params.note);
          });
          const resp = parseResponse(await client.sendXml(xml));
          const result = extractImportResult(resp);
          return result.success
            ? ok(`Service record created. ${result.message}${result.producedId ? ` ID: ${result.producedId}` : ""}`)
            : err(`Failed: ${result.message}`);
        } catch (e) {
          return err((e as Error).message);
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, the description omits whether this generates an ID, handles duplicates, requires specific permissions, or what success/failure looks like. No mention of side effects or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At only 6 words, this is under-specified rather than appropriately concise. Every sentence should earn its place, but this single sentence merely restates the function without adding value. No front-loaded critical information or structure.

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

Completeness1/5

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

Given this is a mutation tool with 4 parameters, no annotations, no output schema, and integration with an external ERP system (POHODA), the description is grossly incomplete. It lacks behavioral details, return value information, and parameter explanations necessary for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (date and text have descriptions; partnerName and note do not). The description fails to compensate for these gaps by explaining the semantics of partnerName (is this a customer? supplier? internal code?) or the purpose of the note field. It adds zero parameter context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a service record in POHODA' is tautological, essentially restating the tool name (create_service). While it identifies the target system (POHODA), it fails to define what constitutes a 'service' record in this context or distinguish it from sibling tools like create_contract, create_order, or create_invoice.

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

Usage Guidelines1/5

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

No guidance provided on when to use this tool versus alternatives. Given the extensive list of sibling creation tools (create_invoice, create_order, create_contract, etc.), the description offers no criteria for selecting this specific tool or prerequisites for invocation.

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/hlebtkachenko/pohoda-mcp'

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