Skip to main content
Glama

Lovie Company Formation

Get Metrics Snapshot

updates_get_metrics_snapshot
Read-only

One month's numbers from the company's posted books, as the accounting overview shows them: revenue, expenses, net income, cash at the month's end and its change, net burn (the average monthly fall in cash over the three months ending that month; 0 and not_burning when cash grew) and runway in whole months. Leave month empty for the last complete month, or pass YYYY-MM for one the founder names. When has_activity is false the books have nothing posted yet: say so and quote no figure. Quote these figures as given; the books hold no recurring revenue or headcount, so never estimate them. 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": "updates_get_metrics_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNo
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
snapshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds real behavior: the has_activity=false empty-books case, a precise definition of net burn including the 0/not_burning case when cash grew, runway expressed in whole months, and the constraint that recurring revenue and headcount are absent so they must never be estimated. That is substantive context beyond the annotations, though nothing is said about caching or freshness of the posted numbers.

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 most important content (what the figures are) is front-loaded, and each later sentence carries a distinct operational rule rather than repeating the schema. The single dense paragraph packs several instructions together, which slightly reduces scannability but contains no filler sentences.

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 field enumeration is a bonus rather than a necessity, and the description still covers the edge case (no posted books), the month default, and data-availability limits. It omits nothing critical for correct invocation, though a hint about which month range is valid beyond the regex would close the last gap.

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?

Schema coverage is only 50% and the month parameter has no schema description, so the description must carry it: it supplies the YYYY-MM format and the default behavior when the field is empty. The companyId wrapper is left to the schema's minimal 'UUID value wrapper' text, which keeps this short of a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource and enumerates its contents (revenue, expenses, net income, cash and its change, net burn, runway) and defines scope as one month from the posted books. An agent can tell it produces a computed monthly metrics summary rather than a ledger, P&L, or balance sheet, even though no sibling is named explicitly.

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?

It gives concrete invocation rules: leave month empty for the last complete month, or pass YYYY-MM for a month the founder names, and it prescribes the response when has_activity is false (say so, quote no figure). It does not route the agent to or away from sibling accounting tools such as accounting_get_profit_and_loss, so the when-not guidance is incomplete.

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.