Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_create_address

Add new contacts or companies to the POHODA address book with required name and optional details like address, ID numbers, and contact information.

Instructions

Create a new address/contact in POHODA addressbook. Requires name; optional fields: street, city, zip, IČO, DIČ, email, phone, web, note.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCompany or contact name (required)
streetNoStreet address
cityNoCity
zipNoZIP/postal code
icoNoIČO (company ID number)
dicNoDIČ (VAT ID)
emailNoEmail address
phoneNoPhone number
webNoWebsite URL
noteNoNote or comment

Implementation Reference

  • The implementation of 'pohoda_create_address' tool, including its registration, input validation schema using Zod, and the handler function that builds the XML import document and sends it to the POHODA client.
      "pohoda_create_address",
      "Create a new address/contact in POHODA addressbook. Requires name; optional fields: street, city, zip, IČO, DIČ, email, phone, web, note.",
      {
        name: z.string().describe("Company or contact name (required)"),
        street: z.string().optional().describe("Street address"),
        city: z.string().optional().describe("City"),
        zip: z.string().optional().describe("ZIP/postal code"),
        ico: z.string().optional().describe("IČO (company ID number)"),
        dic: z.string().optional().describe("DIČ (VAT ID)"),
        email: z.string().optional().describe("Email address"),
        phone: z.string().optional().describe("Phone number"),
        web: z.string().optional().describe("Website URL"),
        note: z.string().optional().describe("Note or comment"),
      },
      async (params) => {
        try {
          const xml = buildImportDoc({ ico: client.ico }, (item) => {
            const adb = item.ele(NS.adb, "adb:addressbook").att("version", "2.0");
            const header = adb.ele(NS.adb, "adb:addressbookHeader");
            header.ele(NS.adb, "adb:addressbookType").txt("company");
            const identity = header.ele(NS.adb, "adb:identity");
            const typAddr = identity.ele(NS.typ, "typ:address");
            typAddr.ele(NS.typ, "typ:name").txt(params.name);
            if (params.street) typAddr.ele(NS.typ, "typ:street").txt(params.street);
            if (params.city) typAddr.ele(NS.typ, "typ:city").txt(params.city);
            if (params.zip) typAddr.ele(NS.typ, "typ:zip").txt(params.zip);
            if (params.ico) typAddr.ele(NS.typ, "typ:ico").txt(params.ico);
            if (params.dic) typAddr.ele(NS.typ, "typ:dic").txt(params.dic);
            if (params.email) header.ele(NS.adb, "adb:email").txt(params.email);
            if (params.phone) header.ele(NS.adb, "adb:phone").txt(params.phone);
            if (params.web) header.ele(NS.adb, "adb:web").txt(params.web);
            if (params.note) header.ele(NS.adb, "adb:note").txt(params.note);
          });
          const response = await client.sendXml(xml);
          const result = extractImportResult(parseResponse(response));
          return result.success
            ? ok(`Address created successfully. ${result.producedId != null ? `ID: ${result.producedId}` : result.message}`)
            : err(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 full disclosure burden. It states the creation action but omits critical behavioral details: whether it returns the created record ID, how it handles duplicates, error conditions, or whether the operation is idempotent.

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 a single, front-loaded sentence that immediately states the action. The semicolon-separated list of optional fields is slightly dense but efficiently presented without extraneous text.

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

Completeness3/5

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

For a 10-parameter creation tool with no output schema or annotations, the description covers the basic operation and parameter enumeration but lacks completeness regarding return values, success/failure behaviors, and integration with the broader address lifecycle (create vs update workflows).

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?

With 100% schema description coverage, the schema already documents all fields. The description lists optional fields but adds minimal semantic value beyond the schema (e.g., no format guidance for IČO/DIČ, no validation rules, no examples).

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 specific action ('Create') and target resource ('new address/contact in POHODA addressbook'), distinguishing it from siblings like pohoda_update_address and pohoda_list_addresses through the 'Create' verb.

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

Usage Guidelines3/5

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

While it notes the required parameter ('Requires name'), it lacks explicit guidance on when to use this tool versus pohoda_update_address or whether duplicate checking occurs. Usage relative to alternatives is implied rather than stated.

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