Skip to main content
Glama

Create activity

well_create_activity

Log the sender's time on a live project in this workspace.

Pass project_id from well_list_projects when it is known. A chat turn may pass the exact full project_name instead; Well writes only when that name matches exactly one live project after case, accent and surrounding-space normalization. If no project matches or more than one does, Well returns numbered choices and waits for the sender to pick one from the project candidates. Never choose by a partial or similar name. MCP calls must pass project_id.

Pass project_id or project_name, duration_seconds and day when the sender named a day. day uses YYYY-MM-DD. For today or no named day on a non-Harvest order, omit day; never compute today's date yourself. Well fills today in the sender's time zone when that zone is known. With no known zone, ask which day the hours were on and never guess. A Harvest request must name its day. duration_seconds is a positive whole number. The sender is the person whose hours are logged. A live project and sender must still belong to this workspace. A complete typed request that names Harvest and a day confirms the local save; the Harvest entry is sent only after the person approves its card.

Set also_in_harvest only when the sender explicitly asked to log this time in Harvest. Pass harvest_workspace_connector_id from a live Harvest row in well_list_connectors when available. The Harvest bridge call must include the returned activity_id outside its args. The bridge reads active Harvest task assignments before it writes and asks the sender to choose if several match.

The receipt states the saved day, the project's week total from activity.week.total_hours, and its sources from activity.week.source_ids. It names a source only when source_ids holds one source; with two it states the total and names no source until the mixed-week wording is decided.

Input Schema

NameRequiredDescriptionDefault
dayNoThe activity day, YYYY-MM-DD; defaults to today in the sender's time zone.
project_idNoThe public id of a live project returned by well_list_projects.
project_nameNoThe exact full name of a live project in this workspace.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
also_in_harvestNoSet only when the person's complete typed request names Harvest too.
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.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
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.
duration_secondsYesThe time the sender logged, in whole seconds.
harvest_workspace_connector_idNoThe live Harvest connection id from well_list_connectors, when one is connected.

Output Schema

NameRequiredDescriptionDefault
codeNo
errorNo
successYes
activityNo
candidatesNo
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
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.
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.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedOutput schema / properties / candidates / items / properties / client_name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / candidates / items / properties / client_name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / near_candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "company_id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "company_id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / near_candidates_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / reply_lines
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed4 schema fields changed
    • addedInput schema / properties / project_name
      Added value: +{
      +  "description": "The exact full name of a live project in this workspace.",
      +  "maxLength": 255,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "project_id",
      -  "duration_seconds"
      -]New value: +[
      +  "duration_seconds"
      +]
    • addedOutput schema / properties / candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "client_name": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "project_id": {
      +        "format": "uuid",
      +        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "project_id",
      +      "name",
      +      "client_name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
  3. Changed6 schema fields changed
    • addedInput schema / properties / also_in_harvest
      Added value: +{
      +  "description": "Set only when the person's complete typed request names Harvest too.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / harvest_workspace_connector_id
      Added value: +{
      +  "description": "The live Harvest connection id from well_list_connectors, when one is connected.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / activity / properties / harvest
      Added value: +{
      +  "oneOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "status": {
      +          "const": "requested",
      +          "type": "string"
      +        },
      +        "workspace_connector_id": {
      +          "format": "uuid",
      +          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "status"
      +      ],
      +      "type": "object"
      +    }
      +  ]
      +}
    • removedOutput schema / properties / activity / properties / week / properties / source_id
      Removed value: -{
      -  "const": "well",
      -  "type": "string"
      -}
    • addedOutput schema / properties / activity / properties / week / properties / source_ids
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "well",
      +      "harvest"
      +    ],
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedOutput schema / properties / activity / properties / week / required
      Previous value: -[
      -  "from",
      -  "to",
      -  "total_hours",
      -  "total_duration_seconds",
      -  "source_id"
      -]New value: +[
      +  "from",
      +  "to",
      +  "total_hours",
      +  "total_duration_seconds",
      +  "source_ids"
      +]
  4. Added

TDQS

A4.4/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 write; the description adds the real behavior: exact-name matching with normalization, numbered-choice fallback instead of fuzzy guessing, time-zone-derived day default, and a two-step save where the Harvest entry is sent only after the person approves its card. These are material behaviors an agent could not infer from the annotations.

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?

Purpose and the project/day rules are front-loaded, which is good, but the final paragraph details receipt fields (activity.week.total_hours, source_ids) even though an output schema exists, and lines like 'the sender is the person whose hours are logged' are filler. The density is justified by tool complexity, but some of the length is not.

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 10-parameter write tool with Harvest bridging and ambiguity handling, the description covers selection, defaults, failure paths, and the approval gate. With annotations and an output schema both present, nothing an agent needs in order to invoke it correctly appears to be 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 coverage is 100%, so the baseline would be 3, but the description adds precedence and constraint meaning the schema does not: project_id is the path for MCP calls, day must never be computed by the agent, duration_seconds must be a positive whole number, and the Harvest connector id comes from a live row in well_list_connectors. This meaningfully exceeds the schema text.

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?

The opening sentence gives a specific verb and resource: logging the sender's time against a live project in the workspace, which separates it from well_list_activities and well_update_activity. It does not name a sibling explicitly, so differentiation is implied rather than stated.

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 conditions throughout: pass project_id from well_list_projects when known, project_name only when it normalizes to exactly one live project, omit day for today unless Harvest, and set also_in_harvest only on an explicit request. Alternatives and failure paths (number of matches, ambiguous Harvest tasks) are spelled out, leaving little to inference.

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