Skip to main content
Glama

get_monthly_books_review

Read-only

Review one calendar month's recorded income, spending, net, top categories/merchants and unusual alerts ('monthly review', 'how did last month go', 'what did I make and spend'). Defaults to last completed month. Advisory estimates are not tax advice. closeReadiness gives recorded-book checks/Action Needed links; explain unknown coverage/limits. Never closes books or certifies tax completeness.

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_monthly_books_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoCalendar month in YYYY-MM format. Defaults to the last completed month.
clientEmailNoAccountants: accepted client email only.

Output Schema

NameRequiredDescriptionDefault
dataNo
messageNo
successYes
closeReadinessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / closeReadiness / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / closeReadiness / properties
      Removed value: -{
      -  "actionNeeded": {
      -    "items": {
      -      "additionalProperties": true,
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "checks": {
      -    "additionalProperties": {
      -      "enum": [
      -        "ready",
      -        "needs_action",
      -        "blocked",
      -        "unknown",
      -        "not_applicable"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  "status": {
      -    "enum": [
      -      "ready",
      -      "needs_action",
      -      "blocked",
      -      "unknown"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -true
  2. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Accepted client's account email (accountants only)."New value: +"Accountants: accepted client email only."
  3. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Client account email. Accountants may use this only for an accepted ExpenseBot client."New value: +"Accepted client's account email (accountants only)."
  4. Changed1 schema field changed
    • addedOutput schema / properties / closeReadiness
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "actionNeeded": {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "checks": {
      +      "additionalProperties": {
      +        "enum": [
      +          "ready",
      +          "needs_action",
      +          "blocked",
      +          "unknown",
      +          "not_applicable"
      +        ],
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "enum": [
      +        "ready",
      +        "needs_action",
      +        "blocked",
      +        "unknown"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "data": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success"
      +  ],
      +  "type": "object"
      +}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "description": "Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple.",
      -  "properties": {
      -    "data": {
      -      "additionalProperties": true,
      -      "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
      -      "type": "object"
      -    },
      -    "error": {
      -      "additionalProperties": true,
      -      "description": "Present only when success === false.",
      -      "properties": {
      -        "code": {
      -          "type": "string"
      -        },
      -        "hint": {
      -          "type": "string"
      -        },
      -        "message": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "message": {
      -      "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
      -      "type": "string"
      -    },
      -    "sampleMeta": {
      -      "additionalProperties": true,
      -      "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
      -      "properties": {
      -        "isTruncated": {
      -          "type": "boolean"
      -        },
      -        "sampleCount": {
      -          "type": "integer"
      -        },
      -        "totalCount": {
      -          "type": "integer"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "success": {
      -      "description": "False on tool errors; check before reading `data`.",
      -      "type": "boolean"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  7. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: advisory estimates are not tax advice, closeReadiness exposes recorded-book checks and Action Needed links, unknown coverage/limits must be explained, and the tool will not close books or certify tax completeness. That is meaningful disclosure of scope limits rather than a restatement of annotations.

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?

Front-loads the resource and scope, then example utterances, then limits, in a compact sequence with no filler sentences. The middle section is telegraphic enough that clauses like 'closeReadiness gives recorded-book checks/Action Needed links' take a second read, but nothing is wasted.

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 an output schema present, the description need not describe return fields, and it still explains defaults, the advisory/tax disclaimer, and what closeReadiness signals. For a read-only two-parameter review tool this is nearly complete; only explicit routing to sibling reporting tools is absent.

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 100% and both parameters are documented in the schema, including the YYYY-MM pattern and the accountant clientEmail restriction. The description merely repeats the 'defaults to last completed month' behavior and does not clarify the accountant/clientEmail relationship or how period interacts with the review scope, so it adds no meaning beyond the schema.

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 verb and resource ('Review one calendar month's recorded income, spending, net, top categories/merchants and unusual alerts') and enumerates exactly what the review covers, which separates it from single-metric siblings like get_pnl or get_spending_summary. It does not name any sibling outright, so the differentiation is implicit in the scope rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Supplies concrete user phrasings ('monthly review', 'how did last month go', 'what did I make and spend') and states the default period, giving an agent a clear trigger condition. It also sets a boundary ('Never closes books or certifies tax completeness'), but it never routes the agent to an alternative tool for custom date ranges or per-metric questions.

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.