Skip to main content
Glama
Sign In
ops-platform-mcp

ops-platform-mcp

by ericthlai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

utilization_report

Retrieve per-employee utilization for a specified week, showing logged hours against weekly capacity and utilization percentage. Use this to identify over or under capacity employees.

Instructions

Per-employee utilization for one week: logged hours against weekly capacity, with a utilization_pct per person. Use this for questions like 'who is over or under capacity' or 'pull this week's utilization'. week is an ISO week string such as '2026-W24'; omit it for the current week. Returns the week's start/end dates and one row per employee (including employees with zero logged hours).

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": "utilization_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: returns one row per employee including zero hours, week start/end dates, and parameter default handling. No contradictions.

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?

Four sentences, front-loaded with purpose, each sentence adds value (purpose, usage, parameter, return structure). 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?

Describes return fields (week dates, per-employee rows with utilization_pct) without output schema. Missing explicit output structure (e.g., array), but adequate for low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only parameter 'week' has 0% schema coverage, but description explains ISO week string format and default behavior (current week if omitted), adding critical meaning beyond schema.

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?

Description clearly states 'Per-employee utilization for one week' with specific metrics (logged hours, capacity, utilization_pct), distinguishing it from siblings like get_project_hours.

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?

Provides explicit use case examples ('who is over or under capacity') and parameter guidance (ISO week format, omit for current week), but does not explicitly exclude alternatives or mention when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools