Skip to main content
Glama

retrieve_work_item_activity

Read-only

Retrieve a single activity log entry for a work item by providing the project, work item, and activity IDs.

Instructions

Retrieve a specific activity for a work item.

Args: project_id: UUID of the project work_item_id: UUID of the work item activity_id: UUID of the activity

Returns: WorkItemActivity object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
activity_idYes
work_item_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
verbNo
actorNo
epochNo
fieldNo
issueNo
commentNo
projectYes
new_valueNo
old_valueNo
workspaceYes
created_atNo
deleted_atNo
updated_atNo
attachmentsNo
issue_commentNo
new_identifierNo
old_identifierNo
Behavior3/5

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

Annotations already provide readOnlyHint=true, so the description's mention of 'Retrieve' is consistent. It adds the return type 'WorkItemActivity object' but does not disclose what happens if the activity is not found or any other behavioral traits.

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?

The description is concise with no wasted words, front-loading the purpose. Every part adds value, and the structure is clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and has an output schema, but the description does not explain what an activity is or mention potential error cases. Adequate for a simple retrieval but could be more informative.

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?

The schema coverage is 0%, but the description lists all three parameters and describes them as 'UUID of the project', etc., adding meaning beyond the bare schema types. However, it lacks additional details such as format constraints or examples.

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 the action 'Retrieve a specific activity for a work item', using a specific verb and resource. It distinguishes itself from the sibling 'list_work_item_activities' by specifying 'specific activity'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives like list_work_item_activities. The usage is implied (when you have an activity ID), but no exclusions or context are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bl4nk44/plane-ce-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server