Skip to main content
Glama

activity_write

Idempotent

Append bounded activity metadata to the project history; does not execute the activity being described. Compatibility dispatcher; prefer the individually named tool when available. Select operation and its matching payload. Supported operations: record_activity. Effects and required fields depend on that operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYesArguments for the selected operation. Follow its matching oneOf branch; fields and side effects differ by operation.
operationYesExact operation to dispatch; prefer its individually named tool when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / oneOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "operation": {
      -        "const": "record_activity",
      -        "type": "string"
      -      },
      -      "payload": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "details": {
      -            "additionalProperties": false,
      -            "properties": {
      -              "referenceIds": {
      -                "items": {
      -                  "maxLength": 500,
      -                  "minLength": 1,
      -                  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -                  "type": "string"
      -                },
      -                "maxItems": 100,
      -                "type": "array",
      -                "uniqueItems": true
      -              },
      -              "status": {
      -                "maxLength": 200,
      -                "minLength": 1,
      -                "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -                "type": "string"
      -              },
      -              "summary": {
      -                "maxLength": 240,
      -                "type": "string"
      -              }
      -            },
      -            "type": "object"
      -          },
      -          "executionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "idempotencyKey": {
      -            "maxLength": 128,
      -            "minLength": 16,
      -            "pattern": "^[A-Za-z0-9_-]+$",
      -            "type": "string"
      -          },
      -          "projectId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          },
      -          "sessionId": {
      -            "maxLength": 200,
      -            "minLength": 1,
      -            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "projectId",
      -          "idempotencyKey"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "operation",
      -      "payload"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "operation": {
      +        "const": "record_activity",
      +        "description": "Select this exact operation; payload must match this branch.",
      +        "type": "string"
      +      },
      +      "payload": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "details": {
      +            "additionalProperties": false,
      +            "description": "Optional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content.",
      +            "properties": {
      +              "referenceIds": {
      +                "items": {
      +                  "maxLength": 500,
      +                  "minLength": 1,
      +                  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +                  "type": "string"
      +                },
      +                "maxItems": 100,
      +                "type": "array",
      +                "uniqueItems": true
      +              },
      +              "status": {
      +                "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +                "maxLength": 200,
      +                "minLength": 1,
      +                "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +                "type": "string"
      +              },
      +              "summary": {
      +                "maxLength": 240,
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "executionId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          },
      +          "idempotencyKey": {
      +            "description": "Caller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action.",
      +            "maxLength": 128,
      +            "minLength": 16,
      +            "pattern": "^[A-Za-z0-9_-]+$",
      +            "type": "string"
      +          },
      +          "projectId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          },
      +          "sessionId": {
      +            "description": "Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.",
      +            "maxLength": 200,
      +            "minLength": 1,
      +            "pattern": "^[A-Za-z0-9][A-Za-z0-9._:@+~-]*$",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "projectId",
      +          "idempotencyKey"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "operation",
      +      "payload"
      +    ],
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / operation / description
      Added value: +"Exact operation to dispatch; prefer its individually named tool when available."
    • addedInput schema / properties / payload / description
      Added value: +"Arguments for the selected operation. Follow its matching oneOf branch; fields and side effects differ by operation."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower, and the description adds real context: it is append-only metadata and it does not execute the described activity. However, 'Effects and required fields depend on that operation' is a non-disclosure for a dispatcher with exactly one operation, leaving mutation effects unstated.

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 actual effect and the non-effect in the first sentence, and the whole thing is four compact sentences. The trailing 'Effects and required fields depend on that operation' is padding given a single supported operation.

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?

For a write tool with full annotation coverage and a 100%-documented schema, the definition covers purpose, dispatch semantics, and the key non-effect. It lacks a statement of the resulting state on success, but with no output schema required and safety already annotated, nothing essential is missing.

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 description coverage is 100% and the schema is unusually rich (idempotencyKey guidance, projectId sourcing, bounded details), so the schema does the heavy lifting. The description only restates the dispatch shape ('Select operation and its matching payload') without adding format or constraint meaning beyond 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?

States a specific verb and resource ('Append bounded activity metadata to the project history') and immediately clarifies what it does NOT do ('does not execute the activity being described'). It also distinguishes itself from siblings by labeling itself a compatibility dispatcher that should be skipped in favor of the individually named tool, so an agent can tell it apart from record_activity.

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?

Explicitly routes the agent: 'prefer the individually named tool when available,' which names the alternative (record_activity) and the condition for preferring it. It stops short of stating the positive trigger (use this only when the named tool is unavailable) and gives no exclusions beyond that.

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