Skip to main content
Glama

get_workspace_daily_trends

Read-onlyIdempotent

Daily activity for this workspace over a date range (default last 30 days, max 366): run volume and outcomes, active members, console sessions, MCP calls, playbook and skill executions, and LLM tokens. Only days with activity are returned; treat missing days as zero. Use for usage trends; use get_workspace_roi for time/value saved.

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

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`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds non-obvious behavior not in annotations: default last-30-days window, 366-day maximum, and sparse output ('Only days with activity are returned; treat missing days as zero'). It stops short of describing aggregation semantics (e.g. timezone of day bucketing beyond UTC) or result ordering, keeping it from a 5.

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?

Two sentences, front-loaded with the resource and metric list, then the sparse-data caveat, then the sibling routing. No redundant restatement of the name or annotations; every 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?

With no output schema, the description does explain what the response contains (metric families, sparse days as zero), which is the main gap it must cover for a read-only aggregation tool. Missing only minor details such as per-day bucketing/ordering, which are unlikely to change invocation decisions.

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 defaults and formats are already documented for `from` and `to`. The description contributes the max-366-day bound, which the schema does not state, adding genuine constraint meaning beyond the structured fields.

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 resource (daily workspace activity) plus an enumerated set of metrics (run volume and outcomes, active members, console sessions, MCP calls, playbook/skill executions, LLM tokens) and scopes it to a date range. It also explicitly disclaims a sibling ('use get_workspace_roi for time/value saved'), so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives direct when-to-use guidance ('Use for usage trends') and names the concrete alternative tool with the condition that selects it (time/value saved → get_workspace_roi). The default window and 366-day cap further pin down expected invocation context.

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