Skip to main content
Glama

Get resource utilization

get_resource_utilization
Read-onlyIdempotent

Get team resource utilization summary showing target hours, actual hours, billable hours, and utilization percentage for the organization. utilizationOnClockHours is true when the utilization figures count clock hours (entries logged in parallel share the clock) rather than logged hours - say 'on clock hours' when it is true; logged-hour totals stay on logged hours either way.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_resource_utilization"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesEnd date for the utilization period (ISO 8601 format, e.g. 2026-01-31)
start_dateYesStart date for the utilization period (ISO 8601 format, e.g. 2026-01-01)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious semantics beyond that: it explains the difference between clock-hour and logged-hour utilization and instructs the agent to label results accordingly. It stops short of explaining aggregation granularity (per person vs per team) or period boundaries.

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

Conciseness3/5

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

The purpose is front-loaded and the first sentence is tight. The second sentence is a single dense clause chain that is hard to parse on first read, and the instruction to 'say on clock hours when it is true' refers to a field that appears in neither the input nor any output schema, which costs clarity.

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?

For a read-only two-parameter report with no output schema, naming the returned metrics is valuable and largely sufficient. The one gap is the utilizationOnClockHours flag: it is described as behaviorally important but is not part of the declared input or output contract, so the agent cannot know how to observe it.

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%, with both start_date and end_date documented as ISO 8601 with examples, so the baseline of 3 applies. The description adds nothing about the two date parameters — no inclusive/exclusive boundary, no maximum range, no timezone handling — leaving the schema to carry the full load.

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?

States a specific verb and resource ('Get team resource utilization summary') and enumerates the metrics returned: target hours, actual hours, billable hours, and utilization percentage, scoped to the organization. It does not distinguish itself from adjacent tools such as get_hours_summary or get_frame_order_utilization, so an agent cannot rule out overlap from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no exclusions or alternatives named, despite a crowded sibling set of reporting tools (get_hours_summary, get_dashboard_metrics, get_financial_analytics). The only conditional guidance concerns how to phrase output when utilizationOnClockHours is true, which is presentation advice rather than tool selection advice.

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