Skip to main content
Glama
Sign In
monarch-mcp2-obot

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Budget Get Budget Category

budget_get_budget_category
Read-onlyIdempotent

Fetch budget details for a specific category and month. Choose summary or full output, and optionally filter to only the fields you need.

Instructions

Get budget category.

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": {
      "month": "<month>",
      "category_id": "<category_id>"
    },
    "name": "budget_get_budget_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYes
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
category_idYes
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond this: it does not mention how month or category_id are interpreted, what happens with missing data, or what output shape to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than effective conciseness. A single vague sentence does not earn its place because it conveys almost no information beyond the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with required parameters and no output schema, the description should clarify required input semantics, return behavior, and relationship to sibling tools. None of that is present. The annotations cover safety, but the description leaves too much to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: the fields and output_mode parameters have descriptions, but the required month and category_id parameters have no descriptions in the schema. The description 'Get budget category' does not compensate by explaining the expected format, semantics, or relationship of these parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('budget category') and implies a read operation ('Get'), so the basic purpose is clear. However, it is so terse that it does not distinguish this tool from siblings like categories_get_category or budget_get_budget, and it offers no detail about scope or what a 'budget category' means in this API.

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 about when to use this tool instead of related tools such as categories_get_category, budget_get_budget, or budget_list_budget_months. The context is only implied by the name and parameters, not explicitly stated.

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