savi-tools

Time summary

get_time_summary

Read-only

Hours logged over a period, split billable vs. non-billable and broken down by project. Answers "how many hours did I bill last month?"

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No	A 4-digit year, or this_year / last_year / this_quarter / last_quarter. Omit for the current fiscal year.
`project`	No	Optional project name to filter to.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`period`	Yes
`byProject`	Yes
`entryCount`	Yes
`totalHours`	Yes
`billableHours`	Yes
`nonBillableHours`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "billableHours": {
+      "type": "number"
+    },
+    "byProject": {
+      "items": {
+        "properties": {
+          "billableHours": {
+            "type": "number"
+          },
+          "hours": {
+            "type": "number"
+          },
+          "projectName": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "projectName",
+          "hours",
+          "billableHours"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "entryCount": {
+      "type": "number"
+    },
+    "nonBillableHours": {
+      "type": "number"
+    },
+    "period": {
+      "type": "string"
+    },
+    "totalHours": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "period",
+    "totalHours",
+    "billableHours",
+    "nonBillableHours",
+    "entryCount",
+    "byProject"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety. It adds the behavioral detail of splitting billable vs non-billable and breaking down by project, but nothing beyond annotations.

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, no wasted words, to the point.

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 output schema present, description is complete enough. It explains the tool's capability and provides an example, which is sufficient for a simple query tool with optional filters.

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%, so baseline is 3. The description does not add meaning beyond the schema (e.g., period and project are mentioned but not elaborated).

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?

The description clearly states it retrieves hours logged over a period, split by billable vs non-billable and by project, which is a specific verb+resource. It distinguishes from sibling tools like get_cash_summary or get_mileage_summary.

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?

The example 'how many hours did I bill last month?' provides clear context for when to use the tool. However, it does not explicitly mention when not to use it or name alternative tools.

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

All savi-tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?