Skip to main content
Glama
Sign In
drebedengi-mcp

drebedengi-mcp

by hawk911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Создать категорию / источник / счёт / тег

create_category

Creates expense categories, income sources, accounts, or tags for home accounting, with optional parent assignment for nested categories.

Instructions

Создать категорию расходов (kind=category), источник дохода (source), счёт (account) или тег (tag).

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": {
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "create_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
parentNoРодитель (для вложенных категорий)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and only says "create". It does not disclose whether duplicate names are rejected, whether `parent` must reference an existing entity, what permissions or workspace scoping apply, or what the response contains after creation. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence that enumerates the four creation modes with no filler. The kind-to-meaning mapping is packed efficiently and appears immediately, so an agent gets the core routing information first.

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?

Slightly overstated—should be 3. Let me revise: the tool has 4 params, no annotations, no output schema, and the caller does not learn what happens after creation (returned ID? defaults for description/parent?). For a create tool with no structured behavioral hints, the description should say more about side effects and required context.

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 description coverage is only 25% (only `parent` is documented), so the description must compensate. It usefully explains the four `kind` values, which is meaning beyond a bare enum list, but says nothing about the `name` constraints (minLength 1) or what the `description` parameter describes, which is ambiguous given the tool description is also called description.

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 pairs a specific verb ("Создать") with four concrete resource types and explicitly maps each enum value of `kind` to its meaning (kind=category → расходы, source → доход, account → счёт, tag → тег). This lets an agent distinguish the four creation modes without inspecting the schema. It stops short of distinguishing itself from siblings like add_expense or add_income, which also create entities.

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 is given on when to use this tool versus alternatives such as add_expense, add_income, or add_transfer, even though those siblings overlap conceptually with creating accounts/categories. No prerequisites are stated either — whether `parent` must already exist or whether names must be unique is left entirely to inference.

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