Skip to main content
Glama

Sum logged time

well_sum_logged_time
Read-only

Sum recorded activity duration in the workspace, grouped by the requested month, person and project dimensions. A person group whose participant matched no person carries that participant's email and a null person_id. Billable seconds and hours appear when the participation has a billable reading; the result contains no billable amount or currency conversion. Load the logged-time skill for activity-hour questions; it resolves the period and handles an empty result. Use well_list_activities when the user needs rows. The range is required and spans at most 366 days; ask which shorter period to read when a request exceeds that limit. The total is measured over all matching typed participation rows, not over a page. The total and every group carry source_ids, stable source identifiers: "harvest" for a Harvest-linked activity and "well" for an activity without a Harvest link. Express these sources in the user's language and do not quote the identifiers. When groups_truncated is true, the groups list stops early but the totals still cover every group. A group that totals one whole Monday-to-Monday week on one project carries its hours_url, the web address of that project's logged week; every other group carries null.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
toYesExclusive activity date, YYYY-MM-DD, after `from` and at most 366 days later.
fromYesInclusive activity date, YYYY-MM-DD.
group_byNoDimensions for the returned groups. Defaults to month, person and project.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
errorNo
groupsNo
successYes
source_idsNo
total_hoursNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
groups_truncatedNo
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
total_billable_hoursNo
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
total_billable_secondsNo
total_duration_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedOutput schema / properties / groups / items / properties / billable_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / groups / items / properties / billable_seconds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • removedOutput schema / properties / groups / items / properties / email / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / groups / items / properties / email / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / groups / items / properties / hours_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / groups / items / properties / hours_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / groups / items / properties / source_id
      Removed value: -{
      -  "const": "well",
      -  "type": "string"
      -}
    • addedOutput schema / properties / groups / items / properties / source_ids
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "harvest",
      +      "well"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / groups / items / required
      Previous value: -[
      -  "month",
      -  "person_id",
      -  "email",
      -  "project_id",
      -  "duration_seconds",
      -  "hours",
      -  "hours_url",
      -  "source_id"
      -]New value: +[
      +  "month",
      +  "person_id",
      +  "email",
      +  "project_id",
      +  "duration_seconds",
      +  "hours",
      +  "billable_seconds",
      +  "billable_hours",
      +  "hours_url",
      +  "source_ids"
      +]
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / source_id
      Removed value: -{
      -  "const": "well",
      -  "type": "string"
      -}
    • addedOutput schema / properties / source_ids
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "harvest",
      +      "well"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / total_billable_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / total_billable_seconds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare this is a non-destructive read with openWorldHint=false; the description adds real behavioral context the annotations cannot: billable seconds appear only when a billable reading exists and no amount or currency conversion is returned, the total covers all matching participation rows rather than a page, groups_truncated can stop the group list while totals still cover everything, and an unmatched participant yields an email with a null person_id. That is exactly the extra context the lowered bar for annotated tools asks for.

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

Conciseness4/5

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

Purpose is front-loaded and the later paragraphs are organized by concern (result shape, source_ids, truncation, hours_url, workspace selection). It is on the long side and some result-shape detail overlaps the output schema, but almost every sentence carries a constraint an agent could otherwise get wrong.

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?

For a read-only aggregate with six parameters, an output schema and full annotations, nothing important is missing: range limits, grouping defaults, workspace selection, truncation semantics, empty-result handling, source identifiers and the null-hours_url case are all covered.

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 description coverage is 100%, so the baseline is 3. The description does add operative meaning beyond the schema — which dimension values mean what in the returned groups, and the instruction to ask for a shorter period when the 366-day cap is exceeded — but the multi-workspace paragraph largely restates the workspace_id schema text rather than extending it.

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?

Opens with a specific verb and resource: 'Sum recorded activity duration in the workspace, grouped by the requested month, person and project dimensions.' It also names a sibling it is not ('Use well_list_activities when the user needs rows'), so an agent can separate the aggregate tool from the row-listing tool without consulting 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?

Explicit when-to-use routing is present: load the logged-time skill for activity-hour questions, use well_list_activities when rows are needed, and call directly when the token authorizes one workspace but pass workspace_id when it authorizes several. It also gives the corrective action when the range is too large ('ask which shorter period to read'), which is guidance rather than a schema restatement.

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