Skip to main content
Glama
Sign In
teamwork

teamwork

by sondv5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Teamwork: project updates

project_updates
Read-only

Get health status reports for projects, filter by project IDs, and optionally show only the current update per project.

Instructions

Latest status updates (health reports) posted on projects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
pageSizeNo
activeOnlyNoOnly the latest update per project (default true)
projectIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior3/5

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

The readOnlyHint annotation already covers safety, and the description adds that the data are 'latest' health reports posted on projects. It does not mention pagination behavior, the activeOnly default, or response characteristics, but it does not contradict annotations.

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?

The description is a single, front-loaded sentence with no filler. It is concise, though it borders on under-specification rather than being genuinely informative.

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

Completeness2/5

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

For a list tool with four optional parameters, no output schema, and no usage guidance, this description is too thin. It leaves pagination defaults, return field structure, and filter interactions to be inferred from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 25% schema description coverage, the description needed to compensate for the undocumented page, pageSize, and projectIds parameters, but it provides no parameter-level detail at all. It does not even clarify that projectIds filters to specific projects.

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 description clearly identifies the resource as 'status updates (health reports)' and scopes them to projects, so an agent can tell what the tool returns. However, it does not explicitly distinguish this from sibling tools like latest_activity or list_projects, so it falls short of a 5.

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 guidance on when to use this tool versus siblings such as latest_activity, list_projects, or upcoming_milestones. The description conveys no selection criteria, prerequisites, or exclusions.

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

Deploy Server

Other Tools