Skip to main content
Glama
Sign In
INFATON MCP35

INFATON MCP35

Official
by infaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

import_data

Import data from a JSON array to create or update objects in 1C:Enterprise ERP. Specify the object type, data, and mode (create, upsert, update).

Instructions

Массовый импорт данных из JSON-массива. Создаёт или обновляет объекты.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "full_name": "<full_name>",
      "data": "<data>"
    },
    "name": "import_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesМассив JSON-объектов с данными для импорта
modeNoРежим: create (по умолчанию), upsert, update
full_nameYesТип объекта для импорта, например: Справочник.Номенклатура

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description bears the full burden. It states that the tool creates or updates objects but does not disclose important behavioral traits such as conflict resolution (though hinted by mode), error handling, performance characteristics, or atomicity.

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 is extremely concise with two short sentences conveying essential functionality without redundancy. It is well-structured and front-loaded.

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?

While the description covers the basic purpose, it lacks details on expected input format, batch limits, error behavior, and return values. For a mass import tool, this information would be valuable for correct use.

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?

The input schema has 100% coverage, with all parameters described. The description adds little beyond the schema: it mentions mass import but does not elaborate on parameter usage or constraints. Baseline of 3 is appropriate given high schema coverage.

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 tool's purpose: mass import of data from a JSON array, creating or updating objects. It specifies the verb (import), resource (data), and outcome (create/update), distinguishing it from single-object operations like create_object or update_object.

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 implies usage for bulk operations but does not provide explicit guidance on when to use this tool over alternatives like create_object or update_object, nor does it mention when not to use it.

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

Deploy Server

Other Tools