Skip to main content
Glama

Measure month-to-date spend against the same days last month

well_measure_month_to_date_spend
Read-only

Measure the spend so far this month against the same number of days last month, in a personal space: one comparison per currency, with both figures and their difference.

Quote month_to_date_spend, same_days_last_month_spend and difference as returned, with the two windows in current_window and previous_window. A 0 is a real zero for that window. success: false with personal_space: false means this workspace is not a personal space: say so, and give no figure.

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
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
errorNo
rulesYes
successYes
currenciesYes
current_windowYes
personal_spaceYes
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.
previous_windowYes
excluded_malformedYes
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.
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive behavior, so the bar is lower, but the description adds real context: a zero is a genuine zero per window, and success:false with personal_space:false is a distinct failure mode where the agent must report the workspace is not a personal space and give no figure. It also notes that `rules` enumerates the rules applied to the figures. Return-field formatting is partly delegated to the output schema.

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?

Purpose is front-loaded in the first sentence, and the following paragraphs each cover a distinct concern (field quoting, failure mode, rules, workspace resolution). The workspace-resolution guidance is slightly repetitive across the schema and description but remains efficient.

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 and annotations already present, the description fills the important gaps: failure semantics, zero-value meaning, and workspace selection. It is nearly complete for a read-only measurement tool, though it could say more about the personal-space requirement when the workspace is not eligible beyond the success:false case.

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 description coverage is 100%, so the schema already documents all three parameters, establishing a baseline of 3. The description echoes the workspace_id selection logic but does not clarify conversation_id lifecycle or workspace_scope (family merging semantics) beyond what the schema says.

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 states a specific verb (measure) and resource (spend so far this month vs. same days last month), plus the scope constraint ('in a personal space') and output shape ('one comparison per currency, with both figures and their difference'). This is distinguishable from related measurement siblings such as well_measure_category_trend or well_measure_subscriptions without opening the schema.

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 operational guidance: call directly when the token authorizes one workspace, and pass workspace_id when several are authorized because the read will not guess. The conversation_id keep-alive guidance is also spelled out. It does not, however, name adjacent tools or state when a different measurement tool is preferable.

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