Skip to main content
Glama

get_workspace_roi

Read-onlyIdempotent

Estimated time and labor value saved by playbook runs in this workspace over a date range (default last 30 days, max 366). Returns totals and, unless includePlaybooks is false, a per-playbook breakdown sorted by minutes saved. Only successful runs count. Money is in USD cents. Use when the user asks how much automation is saving.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date (YYYY-MM-DD, UTC, inclusive). Defaults to today.
fromNoStart date (YYYY-MM-DD, UTC, inclusive). Defaults to 30 days before `to`.
includePlaybooksNoInclude the per-playbook breakdown (default true)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: only successful runs count, money is reported in USD cents, results are sorted by minutes saved, and the date range defaults to 30 days with a 366-day cap. It does not explain how the time/labor estimates are derived, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with what the tool measures, then covers defaults, return shape, filtering rule, units, and a usage cue in four tight sentences. Every sentence carries distinct information and nothing is repeated from the schema verbatim beyond what needs reinforcing.

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 no output schema, the description carries the return-value burden and does so: totals plus an optional per-playbook breakdown, sorted, in a stated currency unit. Combined with the date-range defaults and the successful-runs-only rule, an agent has everything needed to call it and interpret results.

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 100%, so the baseline would be 3, but the description adds meaning the schema lacks: the 366-day maximum window and the fact that the breakdown is sorted by minutes saved. It also restates that includePlaybooks=false suppresses the per-playbook breakdown, reinforcing the schema's wording. The extra constraint on range is the main value added.

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 opening clause names a precise resource and metric: 'Estimated time and labor value saved by playbook runs in this workspace over a date range.' That is far more specific than a generic 'get ROI' and clearly separates it from siblings like get_workspace_daily_trends or get_workspace_health. It stops short of a 5 because no sibling is named or explicitly excluded, leaving the agent to infer the boundary.

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?

'Use when the user asks how much automation is saving' gives an explicit triggering condition tied to user intent, which is the most useful kind of routing cue. There is no when-not guidance and no alternative tool is mentioned for adjacent questions (e.g. trends or health), so it is clear but not exhaustive.

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