Skip to main content
Glama

Uninvoiced time

get_uninvoiced
Read-onlyIdempotent

What is not invoiced yet, for an admin or the owner: the hours, amounts and expenses of each client and project, and the totals of each currency. For "what is not invoiced this month", pass from and to as the first and the last day of the month (call whoami for today's date and time zone if needed): the fixed fees left to invoice have no date, so they come apart in fixed_fees, out of the totals. Without from and to, all uninvoiced time.

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

Input Schema

NameRequiredDescriptionDefault
toNoThe last day, with `from`
fromNoThe first day, with `to`

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
rowsYes
totalsYes
fixed_feesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: a role requirement (admin or owner), that fixed fees carry no date and therefore split out into `fixed_fees` excluded from totals, and that results are grouped per client/project with per-currency totals. Return format details are the main omission, and an output schema exists anyway.

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-loaded with what the tool returns, then the parameter behavior, then the default — a sensible order with no filler. The second sentence is a long chained clause ('the fixed fees left to invoice have no date, so they come apart in fixed_fees, out of the totals'), which costs some readability but each clause carries information.

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?

For a two-parameter read-only report with an output schema and full annotation coverage, the description supplies the role requirement, the date-window convention, and the default scope. The remaining ambiguity — date inclusivity and how the fixed_fees split relates to the returned totals — is minor but not zero.

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 the schema already says `to` pairs with `from` and vice versa, so the baseline is 3. The description does add real semantics — both dates should be the first and last day of the month, and omitting them means all-time — but it does not clarify inclusive/exclusive boundaries or time-zone handling of the dates themselves.

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 resource precisely — uninvoiced hours, amounts, expenses per client and project plus per-currency totals — which is a reporting view distinct from the CRUD siblings like get_invoice or list_invoices. It also states the audience (admin or owner). It stops short of explicitly contrasting with any sibling, so it lands at 4 rather than 5.

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 when-to-use guidance keyed to the caller's intent: for 'what is not invoiced this month', pass `from` and `to`; with no dates you get all uninvoiced time. It even routes to `whoami` for the current date and time zone. There is no explicit exclusion (e.g., when to prefer list_invoices), so not a 5.

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