Skip to main content
Glama
sergeyfedyakov

v8help-mcp

by sergeyfedyakov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Config Set

config_set

Update and save v8help.toml settings atomically. Supply flat key-value pairs to change search, build, embedder, and book options.

Instructions

Изменить настройки и сохранить в v8help.toml (атомарно).

Ключи: search.backend (fts|hybrid|vectors), search.limit, search.max_chunks_per_page, build.cleanup, build.chunk_size, build.chunk_overlap, embedder.index/query.{model,base_url,api_key,dims, batch_size,embed_chars,threads}, bin_dir, lang, books.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valuesYesПлоские ключи -> значения.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / values / additionalProperties
      Added value: +true
    • changedInput schema / properties / values / description
      Previous value: -"Плоские ключи -> значения"New value: +"Плоские ключи -> значения."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: the write to v8help.toml is atomic. However it omits mutation semantics that matter here, e.g. whether supplied values merge with existing config or replace it, and whether invalid keys are rejected or silently ignored.

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?

Extremely tight: the mutating action and its atomic persistence are front-loaded in the first clause, followed by a compact key reference list that earns its length by documenting valid configuration keys. No filler sentences.

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?

The output schema covers return values and the parameter is documented, so those needs are met. As a mutation tool with zero annotations, though, the description should say whether updates are partial/merge-style, whether invalid keys error, and whether a restart is needed for changes to take effect.

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 the single 'values' object parameter is already documented, but the description goes beyond the schema by enumerating the recognized keys and giving an enum for one of them (search.backend: fts|hybrid|vectors). That compensates for the schema's permissive additionalProperties, which otherwise gives no key validation guidance.

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 names a specific verb and resource ('Изменить настройки' / change settings) and adds the persistence target ('сохранить в v8help.toml, атомарно'), so an agent knows exactly what the tool mutates. It does not explicitly name the read counterpart (config_get) as the sibling it is not, 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 only implied by the verb 'change settings'; there is no statement of when to use this versus config_get or config_get-style reads, nor any prerequisites or warnings. The agent can infer it is the write path for configuration, but nothing is made explicit.

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