Skip to main content
Glama

Logged time

well_render_logged_time
Read-only

Measure the workspace's logged hours over the trailing 30 days, for a board's logged-time block.

This tool measures, rather than taking a figure you state: a logged-hours total is read straight off the activity rows, with no classification a skill has to settle first. Call it with no arguments and forward its structuredContent WHOLE to well_render_canvas, exactly as a finance block forwards its own render tool's reading. Use well_sum_logged_time instead when the user asked a logged-time question directly: this tool exists only to fill a board block.

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
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
unitNo
errorNo
valueNo
captionNo
displayNo
successYes
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.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: it measures from activity rows rather than accepting a stated figure, and its output is meant to be forwarded wholesale to well_render_canvas. It does not, however, describe the shape or limits of the reading itself.

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?

Front-loaded with the measurement scope, then routing, then parameter conditions — a sensible order. Some phrasing is padded ('with no classification a skill has to settle first', the finance-block analogy), but nothing is misleading or misplaced.

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 zero-required-argument read feeding a render pipeline, the description covers invocation, downstream forwarding, sibling disambiguation and workspace scoping, and an output schema exists so return values need not be explained. Nothing an agent needs in order to call it correctly is missing.

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 goes beyond the schema by explaining the conditional logic for workspace_id (omit with a single authorized workspace, required when several, because the read will not guess) and reinforces the no-argument default, which is the decision an agent actually has to make.

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 verb, resource, scope and time window: 'Measure the workspace's logged hours over the trailing 30 days', and ties it to its only legitimate use, filling a board's logged-time block. It explicitly names the sibling well_sum_logged_time as the different tool, so the 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 explicit when-to-use (fill a board block), when-not-to-use (a direct logged-time question → well_sum_logged_time), and invocation guidance (no arguments, forward structuredContent whole to well_render_canvas). It also covers the workspace condition: call directly with one authorized workspace, pass workspace_id when several.

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