Skip to main content
Glama
Sign In
Budgetsco MCP Server

Budgetsco MCP Server

by drishit96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set Budget

setBudget

Assign spending limits to categories to manage monthly budgets and monitor spending against planned amounts.

Instructions

Set budget for categories

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "setBudget"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / description
      Removed value: -"Parameters for setting budget"
    • removedInput schema / properties / breakdown
      Removed value: -{
-  "additionalProperties": {
-    "anyOf": [
-      {
-        "anyOf": [
-          {},
-          {
-            "type": "string"
-          }
-        ]
-      },
-      {
-        "type": "number"
-      }
-    ]
-  },
-  "description": "Breakdown of the budget by category. Keys are category names, values are budget amounts.",
-  "propertyNames": {
-    "minLength": 1
-  },
-  "type": "object"
-}
    • removedInput schema / required
      Removed value: -[
-  "breakdown"
-]
  2. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

The annotations are all false, providing no hints, so the description must carry the burden. It only states a mutation action ('set') without disclosing side effects, idempotency, permissions, or return behavior. This is insufficient for an agent to safely invoke the tool.

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

Conciseness4/5

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

The description is a single short sentence with no fluff, which is concise and front-loaded. However, it is so terse that it omits necessary details, so while it is concise, it is not fully effective. The structure is acceptable but minimal.

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?

Given that the tool has no parameters, no output schema, and no useful annotations, the description is extremely incomplete. It does not explain what inputs are needed (even though there are none), what the tool returns, or any side effects. An agent would not know how to use this tool effectively or what to expect.

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?

There are zero parameters in the schema, and the description adds no parameter information. According to the rubric, with 0 parameters the baseline is 4, and since there is nothing to explain, this dimension is adequately covered. However, the tool's functionality is questionable without parameters.

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 'Set budget for categories' clearly identifies the action (set) and the resource (budget for categories), and it is distinct from the sibling getBudget. However, it lacks specificity about which categories or budget amounts, and the empty schema suggests the tool cannot actually perform its stated purpose. Overall, it conveys the basic purpose but is minimal.

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?

The description provides no guidance on when to use this tool versus alternatives like getBudget or createCustomCategories. It does not mention any conditions or prerequisites, leaving the agent to infer when a budget should be set. This is a significant gap for a tool that likely requires context.

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