Skip to main content
Glama

Money by day

dosai_get_money_by_day
Read-onlyIdempotent

Day by day for a period: balance at the start and end of each day, what was spent on the bot and what was topped up. Without dates: the default period of the cabinet page. Owner only.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_get_money_by_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds context the agent cannot get from them: the default period applied when from/to are omitted, and an owner-only authorization requirement. It does not cover response shape or pagination, but for a read-only report that is a minor omission.

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?

Two compact sentences: what you get first, then default-period behavior, then the access restriction. Nothing is redundant, though the phrasing 'what was spent on the bot and what was topped up' is telegraphic rather than precise.

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 usefully enumerates the returned figures, and it documents the required project_id source indirectly while flagging the owner-only restriction. The main remaining gap is the date parameter contract, which matters because two of three parameters lack descriptions.

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 coverage is only 33% — project_id is documented, but from and to carry only a date pattern and no description. The description partially compensates by indicating the dates define 'a period' and that they are omittable with a default fallback, but it never states the date format or inclusive/exclusive boundaries.

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 the concrete output — per-day starting/ending balance, bot spend, and top-ups — which is more specific than the name alone and separates it from a plain balance check. It does not explicitly name a sibling tool, so differentiation is inferential rather than stated.

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?

It gives one useful usage rule: omitting dates falls back to the cabinet page's default period, and it notes the 'Owner only' access constraint. It never states when to prefer this over related siblings such as dosai_get_balance or cost-oriented tools, so selection guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources