Skip to main content
Glama
Sign In
INFATON MCP35

INFATON MCP35

Official
by infaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_module_text

Retrieve the source text of a configuration object module. Provide the full object name and optionally the module type to obtain the module code.

Instructions

Получить исходный текст модуля объекта конфигурации. Работает только если расширение имеет доступ к основной конфигурации.

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>"
    },
    "name": "get_module_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_nameYesПолное имя объекта, например: Справочник.Номенклатура
module_typeNoТип модуля: ОбъектМодуль, МодульМенеджера, МодульФормы (по умолчанию ОбъектМодуль)

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?

With no annotations, the description should disclose behavioral traits. It mentions the extension access requirement but omits details on error handling, return format, or side effects. The read-only nature is implied but not stated.

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?

Two sentences, no wasted words. Information is front-loaded: first sentence states purpose, second adds a critical constraint. Excellent for agent readability.

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?

Adequate for a simple read operation, but missing details like what happens if the object doesn't exist or the module is inaccessible. No output schema, so description should cover return expectations. The access constraint is helpful but not fully complete.

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?

Schema covers both parameters with descriptions. The description adds value by specifying the default value for module_type (ОбъектМодуль) and clarifying the format of full_name with an example. This goes beyond the schema.

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?

Description clearly states 'get source text of a module' with a specific verb and resource. The constraint about extension access differentiates it from other get_ tools, making the purpose distinct.

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?

No guidance on when to use this tool versus alternatives like get_object_attributes or get_metadata_tree. The only usage hint is the access precondition, but no explicit recommendations or exclusions.

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