Skip to main content
Glama
hlebtkachenko

POHODA MCP Server

pohoda_company_info

Retrieve company and accounting unit details from POHODA accounting software, including company name, database name, accounting period, and year.

Instructions

Get POHODA company/accounting unit info: company name, database name, accounting period, and year. Requires authenticated connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the pohoda_company_info tool, which fetches and parses company information using a POHODA client.
    server.tool(
      "pohoda_company_info",
      "Get POHODA company/accounting unit info: company name, database name, accounting period, and year. Requires authenticated connection.",
      {},
      async () => {
        try {
          const xml = await client.getCompanyInfo();
          const data = parseCompanyInfoXml(xml);
          const lines: string[] = [];
          if (data.companyName) lines.push(`Company: ${data.companyName}`);
          if (data.databaseName) lines.push(`Database: ${data.databaseName}`);
          if (data.accountingPeriod) lines.push(`Accounting period: ${data.accountingPeriod}`);
          if (data.year) lines.push(`Year: ${data.year}`);
          return ok(lines.length > 0 ? lines.join("\n") : xml);
        } catch (e) {
          return err((e as Error).message);
        }
      }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the authentication requirement and enumerates the specific data fields retrieved, which is helpful. However, it omits other behavioral traits like read-only safety, error conditions, or the response structure/format.

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?

The description consists of two efficient sentences with no wasted words. It is front-loaded with the action verb ('Get') and immediately specifies the resource and returned fields, followed by the authentication prerequisite.

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?

Given the tool's simplicity (zero parameters, no nested objects) and lack of an output schema, the description adequately compensates by enumerating the specific data fields returned (company name, database, period, year). It provides sufficient context for a straightforward metadata retrieval operation.

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

Parameters4/5

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

The input schema contains zero parameters. Per the scoring guidelines, a parameterless tool receives a baseline score of 4, as there are no parameter semantics to clarify beyond the schema itself.

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 uses a specific verb ('Get') and clearly identifies the resource (POHODA company/accounting unit info). It distinguishes itself from sibling CRUD and list operations by targeting the specific company configuration metadata and explicitly listing the returned fields (company name, database name, accounting period, year).

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?

The description states a prerequisite ('Requires authenticated connection') but does not explicitly define when to use this tool versus similar siblings like 'pohoda_status' or 'pohoda_list_settings'. Usage is implied by the specific fields listed (use when you need company metadata), falling short of explicit guidance.

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