Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get budget status

get_period_budget
Read-only

Get the current budget period status: total budget, projected cost, and remaining or over-budget amount. Defaults to today's period; optionally evaluate a specific date.

Instructions

How the current budget period is going: what the budget is, what this period is projected to cost, and how much is left or over. Defaults to the period containing today.

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": "get_period_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
reference_dateNoEvaluate the period containing this YYYY-MM-DD date instead of today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint and openWorldHint already declare the safety profile, so the description only needs to add context. It does add that the cost figure is a projection rather than a settled amount and that the scope is the period containing a date, but says nothing about what happens for future periods or how an unbudgeted period is reported.

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?

One sentence plus a short default clause; the returned fields are front-loaded and every phrase carries information. Nothing is wasted or repeated from the schema.

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?

With no output schema, the description correctly compensates by naming the three values returned (budget, projected cost, remaining/over). For a one-optional-param read tool that is nearly complete; only edge-case behavior for periods with no budget is unaddressed.

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 100% and the single optional parameter is fully documented as a YYYY-MM-DD override. The description's 'defaults to the period containing today' merely corroborates the schema's default behavior rather than adding new semantics, so the baseline of 3 applies.

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 resource (the current budget period) and enumerates what it reports: budget amount, projected cost, and remaining/overage. It's clear what the tool returns, but it never distinguishes itself from the sibling get_monthly_cost, which an agent could plausibly confuse with a period-cost projection.

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?

'Defaults to the period containing today' implies when the tool is relevant (current-period status checks) and how the optional param shifts that window. However, there is no explicit guidance on when to prefer this over get_monthly_cost or update_budget, and no stated 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