Skip to main content
Glama

get_task_seen

Read-onlyIdempotent

Retrieves who opened a task and when, including each person's first and last view.

Instructions

Who has opened a task, and when (first and last view per person).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "get_task_seen"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered elsewhere. The description contributes the useful detail that results are per-person with first and last view timestamps, but says nothing about visibility/permission scoping (e.g. whether all viewers are returned) or handling of tasks with no views.

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?

One sentence, front-loaded with the core question it answers ('who has opened a task, and when') and the parenthetical clarifying the aggregation. No filler, though the sentence is so terse it omits routing information an agent would benefit from.

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?

With only one required parameter, an output schema present, and rich annotations, the definition covers just enough to invoke correctly. It is thin on the two things the structured fields cannot supply: how this differs from get_task_history and whether viewers are permission-scoped.

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 coverage is 0% for the single task_id parameter, so the description is the only source of meaning — it implies the tool operates on exactly one task, which is the correct read. However, it adds no format or source guidance for task_id (ID style, where to obtain it), so it barely compensates for the coverage gap.

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?

Names a specific resource (per-person task view records) and what it returns (who opened the task, first and last view). An agent can distinguish this from a generic get_task or get_task_history, though the description never explicitly contrasts itself with those siblings.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or prerequisite guidance. Nothing tells the agent whether this is the right tool versus get_task_history when it wants activity/audit information on a task.

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