Skip to main content
Glama

Get figure

well_get_figure
Read-only

Measure the business's runway (how long the cash lasts), cash position (the cash it holds now) or average monthly burn, as it stands now, with every check the skill for that figure runs, in one call.

It does not take a forecast or a scenario (a hire, a new cost, a change of revenue: "what if", "if I hire"), a period in the past, one account, one category, a named company, or an explanation of a figure. Its line states the figure as it stands, so it is not a base for a scenario either.

  • success true: card names the card tool that draws the figure (card.tool) and the input to draw it with (card.input). answer_line is the skill's answer line, filled in language.

  • success false: the figure was not measured. reason names the check or step that stopped it. skill is the slug of the skill that measures the figure with its full steps.

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

TableJSON Schema
NameRequiredDescriptionDefault
figureYes"runway" for the months of cash left; "cash_position" for the cash held now; "avg_burn" for the average monthly burn. A question about the cash and the runway together is "runway": the runway line states the cash too.
languageYesThe language of your answer.
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

TableJSON Schema
NameRequiredDescriptionDefault
cardNoThe card tool that draws the figure, and the input to draw it with. Present when `success` is true.
skillNoThe slug of the skill that measures the figure with its full steps. Present when `success` is false.
figureYes
reasonNoThe check or step that stopped the measure. Present when `success` is false.
successYes
answer_lineNoThe skill's answer line, filled in `language`. Present when `success` is true.
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.
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 establish readOnly/safe behavior, but the description adds real operational context: what success returns (card.tool, card.input, answer_line in the chosen language), what failure returns (reason, skill slug), and the multi-workspace refusal-to-guess behavior. It stops short of describing latency, caching, or how the underlying checks are ordered.

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 core purpose and immediately followed by exclusions and the result contract; the bullet structure for success/failure is easy to parse. There is mild redundancy in restating the no-scenario constraint twice ('does not take a forecast or a scenario' / 'not a base for a scenario either').

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?

An output schema exists and the description still sketches the return contract, covering the main ambiguities for a measurement tool with workspace scoping. The remaining gap is the missing pointer to sibling tools for the excluded forecast/period cases, which matters given the dense sibling list.

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 enum descriptions for figure, workspace_id, conversation_id, and workspace_scope are already detailed. The description reinforces the workspace_id convention (pass it when several workspaces are authorized) but adds no syntax or semantics beyond what the schema states.

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 (measure) and enumerates the exact figures produced (runway, cash position, avg monthly burn), plus the distinguishing trait that it runs the full skill in one call. It is clearly separable from the render_* and measure_* siblings, which draw or trend rather than report the figure as it stands now.

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?

Explicitly rules out forecasts/scenarios, past periods, single accounts/categories, and named companies, which is strong negative guidance an agent can act on. It also states the token/workspace precondition for calling directly. It does not, however, name the alternative tool to use for those excluded cases (e.g., a forecast or render tool), so routing is implied rather than given.

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