Skip to main content
Glama

Measure how many days customers take to pay

well_measure_days_to_pay
Read-only

Measure how many days the workspace's customers take to pay: the median and the mean days from a sale invoice's issue date to the day it was paid, over the paid sale invoices settled between from (inclusive) and to (exclusive), both as YYYY-MM-DD.

Quote median_days and mean_days as returned, with the period. Never recompute a gap, and never average the rows yourself. When median_days is null, no invoice in the period has a measured gap: say so, do not say zero. unknown_count is the number of paid invoices left out (no issue date, or a settlement before the issue date); say it beside the figure when it is not zero.

side_unknown: true means the workspace has no resolved own company, so the sale side cannot be told apart: both figures are null and nothing is measured. Say the sale side is unknown.

truncated: true means the period holds more invoices than were read, or an invoice holds more payments than were read, so the figures cover only what was read.

rules states every rule the figures apply.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
sideYes
errorNo
rulesYes
windowYes
successYes
mean_daysYes
truncatedYes
median_daysYes
side_unknownYes
unknown_countYes
measured_countYes
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
missing_date_countYes
negative_gap_countYes
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
settled_invoice_countYes
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly and closed-world; the description goes far beyond by disclosing every failure and edge mode: null median_days meaning no measured gap, side_unknown meaning no resolved own company, truncated meaning invoices or payments were not all read, and rules stating the applied logic. That is exactly the context needed to interpret a figure honestly.

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 the metric, then one short paragraph per edge case (null, unknown_count, side_unknown, truncated, rules) and a closing note on workspace selection. It is long, but nearly every sentence carries a distinct interpretation rule; the framing duplicates a little of what the schema already says about conversation_id and workspace_scope.

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

Completeness5/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 explain return shapes and instead spends its space on the things structure cannot express: boundary semantics, null and unknown meanings, truncation, and workspace prerequisites. Nothing an agent needs to call and correctly narrate the result is missing.

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?

At 60% schema coverage the description carries real weight and does: it specifies that the window is settled date between `from` (inclusive) and `to` (exclusive), both YYYY-MM-DD, and restates the workspace_id rule. conversation_id and workspace_scope are covered by the schema's own descriptions rather than here, so it is not fully self-contained.

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?

States a specific verb and resource and then defines the metric precisely: median and mean days from a sale invoice's issue date to its payment date, over paid sale invoices settled in a stated period. An agent cannot confuse this with any other sibling measurement, since the population, the two endpoints of the gap, and the two statistics are all named.

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?

Gives an explicit precondition for calling it: when the token authorizes one workspace, call directly; when it authorizes several, pass workspace_id rather than guessing. It also instructs on how to use the results (quote as returned, say unknown_count beside the figure, say the sale side is unknown when side_unknown is true). It stops short of naming which sibling measurement to use for an adjacent question.

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