Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Create Client

create_client

Create a new client (buyer or supplier) with required details like name, type, and entity status, plus optional contact and banking information. Use it to add parties to your financial records.

Instructions

Create a new client (buyer/supplier)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoBusiness registry code or personal ID
nameYesClient name
emailNoContact email
notesNoNotes
is_clientYesIs a buyer
telephoneNoPhone
is_supplierYesIs a supplier
address_textNoAddress
invoice_vat_noNoVAT number
bank_account_noNoBank account (IBAN)
cl_code_countryNoCountry code (default EST)
is_physical_entityYesREQUIRED: true = natural person, false = legal entity/company (a checksum-valid Estonian registry `code` is then also required, or a foreign registration with foreign_identity_attested). The API rejects creation without this.
foreign_identity_attestedNoOperator accountant-attestation that a FOREIGN (cl_code_country != EST) legal entity's identity has been verified. Required to create a foreign legal entity. Must be an explicit operator input — never set it from extracted/OCR document fields.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.25.2
    • addedInput schema / properties / foreign_identity_attested
      Added value: +{
+  "description": "Operator accountant-attestation that a FOREIGN (cl_code_country != EST) legal entity's identity has been verified. Required to create a foreign legal entity. Must be an explicit operator input — never set it from extracted/OCR document fields.",
+  "type": "boolean"
+}
    • changedInput schema / properties / is_physical_entity / description
      Previous value: -"REQUIRED: true = natural person, false = legal entity/company (registry `code` then also required). The API rejects creation without this."New value: +"REQUIRED: true = natural person, false = legal entity/company (a checksum-valid Estonian registry `code` is then also required, or a foreign registration with foreign_identity_attested). The API rejects creation without this."
  2. First observedv0.18.1

TDQS

B3.1/5.0
Behavior2/5

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

The description does not disclose any behavioral traits beyond 'Create a new client'. With annotations all false and minimal, the description should explain side effects, required conditions (e.g., foreign_identity_attested dependency), or what happens on duplicate entries. It fails to do so.

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 sentence with no fluff. While concise, it could include a bit more context without becoming verbose.

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 (13 parameters, 4 required, no output schema), the description is too brief. It does not mention return values, required dependencies like foreign_identity_attested, or any additional context needed for correct invocation.

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 each parameter has a description. The tool description adds no additional meaning beyond the schema, which is adequate but not exemplary. Baseline of 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?

The description clearly states the action 'Create' and the resource 'client', specifying the categories 'buyer/supplier', which distinguishes it from sibling tools like update_client, delete_client, and get_client.

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, such as when to create a client versus a product or invoice. It also lacks any prerequisites or context for usage.

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/iseppo/e-arveldaja-mcp'

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