Skip to main content
Glama
sergeyfedyakov

v8help-mcp

by sergeyfedyakov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Page

get_page

Fetch full text of 1C:Enterprise help pages by ID. Supports multiple IDs and returns chunk data for long articles, with optional chunk selection.

Instructions

Полный текст страницы справки по идентификатору (filename без .md или числовой id).

id может быть строкой (одна страница) или массивом строк (несколько страниц одним вызовом, 2-10 статей, пока суммарно не превышено max_chars). Длинные статьи (>4000 символов) целиком НЕ возвращаются: отдаётся список чанков и первый чанк; конкретный чанк читается через chunk=N.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesСтраница или список страниц.
chunkNoНомер чанка (0-based) для чтения части длинной статьи.
max_charsNoЛимит суммарного размера ответа (для массива id).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / chunk / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / chunk / default
      Added value: +null
    • changedInput schema / properties / chunk / description
      Previous value: -"Номер чанка (0-based) для чтения части длинной статьи"New value: +"Номер чанка (0-based) для чтения части длинной статьи."
    • removedInput schema / properties / chunk / type
      Removed value: -"integer"
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / id / description
      Previous value: -"Страница или список страниц"New value: +"Страница или список страниц."
    • removedInput schema / properties / id / oneOf
      Removed value: -[
-  {
-    "description": "Идентификатор страницы",
-    "type": "string"
-  },
-  {
-    "description": "Несколько идентификаторов страниц",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-]
    • addedInput schema / properties / max_chars / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / max_chars / default
      Added value: +null
    • changedInput schema / properties / max_chars / description
      Previous value: -"Лимит суммарного размера ответа (для массива id)"New value: +"Лимит суммарного размера ответа (для массива id)."
    • removedInput schema / properties / max_chars / type
      Removed value: -"integer"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observedv0.10.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that long articles (>4000 chars) are truncated to a chunk list plus first chunk, that chunk=N retrieves a specific part, and that array batching is capped at 2-10 articles / max_chars. It omits auth requirements and not-found behavior, keeping it short of a 5.

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?

Front-loaded with the core purpose, then the id-form and truncation rules in two tight sentences. Every clause conveys a distinct behavioral fact with no filler.

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?

An output schema exists, so return-value documentation is unnecessary. Given the three-parameter tool with batching and chunking complexity, the description covers the important behaviors; only edge cases (missing id, chunk out of range) are left implicit.

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 coverage is 100%, so baseline is 3, but the description genuinely adds meaning beyond the terse schema text: id as string vs array with the 2-10 batching limit, max_chars as an aggregate response cap for arrays, and chunk as the mechanism for reading truncated long articles.

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?

States a specific verb+resource: retrieve the full text of a help page identified by filename (without .md) or numeric id. Purpose is unambiguous, but it never distinguishes itself from siblings like search, related, or discover, so it falls short of a 5.

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?

Usage is implied rather than stated: use it once you already have an id. It gives mechanics (batching, chunking) but no guidance on when to prefer this over search or related for locating content, and no 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