Skip to main content
Glama

Lovie Company Formation

Get Income Rollup

get_income_by_category
Read-only

Total income over a date window grouped into the Money Graph income lenses (Revenue, Capital, Other), optionally per month, with total expenses and net burn. Read-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": {
      "companyId": "<companyId>"
    },
    "name": "get_income_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketNo
dateToNo
monthlyNo
dateFromNo
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
seriesNo
netBurnNo
currencyNo
totalIncomeNo
totalExpensesNo
categoryTotalsNo
incomeByPeriodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the trailing 'Read-only' is largely redundant. The description does add genuine value by disclosing that the response includes total expenses and net burn alongside income, which the tool name hides, but it says nothing about default date windows, permission needs, or how the lenses are derived.

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 tightly written clauses that front-load the aggregation, the grouping, and the optional bucketing, with no filler. The only unearned content is the closing 'Read-only.', which duplicates the annotation.

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

Completeness3/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 needn't explain return values, but for a 5-parameter tool with a nested UUID wrapper and 20% schema coverage it should resolve the bucket-vs-monthly overlap and note that companyId is required. It leaves a real risk of an incorrectly parameterized call.

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 20%, so the description must carry weight and it partially does: 'date window' maps to dateFrom/dateTo and 'optionally per month' touches monthly/bucket. It leaves the key ambiguity unresolved — both a bucket enum (MONTH/DAY) and a monthly boolean exist, and the description never says which governs — and it never mentions the required companyId.

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+resource (total income grouped into Money Graph income lenses) and enumerates the buckets (Revenue, Capital, Other), which makes the output shape concrete. It does not name or differentiate itself from close siblings like get_spending_by_category, spend_get_income_by_payer, or transaction_get_summary, so an agent must infer the boundary.

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?

There is no explicit when-to-use or when-not guidance and no alternative tool is named. 'Over a date window' implies a scoping context but does not tell the agent when this is the right choice versus the spending rollups or P&L siblings.

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.