Skip to main content
Glama

Coline

Read a project's updates

read_project_updates
Read-onlyIdempotent

Lists a project's weekly updates, newest first, each line with the facts behind it.

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": {
      "workspace": "<workspace>",
      "projectId": "<projectId>"
    },
    "name": "read_project_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
projectIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior context: results are ordered newest first and each entry carries supporting facts. It does not mention pagination or how far back the weekly window reaches.

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 front-loaded sentence with no filler; the verb and resource come first and ordering follows. The trailing clause "each line with the facts behind it" is slightly impressionistic rather than informational, which keeps it from a perfect score.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a three-parameter tool with weak schema coverage, the description should at least explain what projectId expects and whether limit bounds the number of weekly entries returned.

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

Parameters2/5

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

Schema coverage is only 33% — workspace is documented in the schema, but projectId and limit are not, and limit's default of 10 plus max of 100 carries real behavioral meaning that is invisible. The description adds no parameter meaning at all, so it fails to compensate for the low coverage.

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?

"Lists a project's weekly updates, newest first" gives a specific verb, a specific resource, and ordering, which is enough to tell it apart from read_project (single project facts) and write_project_update (the write counterpart). It stops short of naming a sibling or scoping the result set beyond the project.

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 statement and no alternative named. An agent cannot tell from the description whether to reach for this or read_board_activity / read_scope_activity when it wants recent project activity; the only implicit signal is the word "weekly".

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