Skip to main content
Glama

get_project_chat

Read-onlyIdempotent

Retrieve a project's group chat messages by project ID or title, with limit and offset controls to page through conversations.

Instructions

The group chat of a project (id or title). Same output as read_chat.

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": {
      "project": "<project>"
    },
    "name": "get_project_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
projectYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile needs no restating. The description adds one genuine behavioral fact (identical output shape to read_chat), but says nothing about pagination behavior (limit 30 / offset 0 defaults), whether a chat is created when absent, or whether the result is metadata versus messages.

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?

Two short sentences with the resource stated first and the output-shape note second; nothing is redundant. The brevity is efficient rather than padded, even if it leaves gaps elsewhere.

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 spelled out and the "same output as read_chat" note is a reasonable shortcut. However, for a three-parameter read tool with zero schema descriptions, the omission of any paging explanation leaves the definition only marginally complete.

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 description coverage is 0%, so the description carries the full burden, yet it only clarifies one of three parameters (project accepts an id or title). limit and offset are completely undocumented in both schema and description, leaving the agent to guess their paging semantics and defaults.

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 names a specific resource and its selector: "The group chat of a project (id or title)." That distinguishes it from read_chat/list_chats by scope (project-scoped vs. arbitrary chat), though the framing is a noun phrase rather than a verb and doesn't say whether it returns chat metadata or messages.

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?

No when-to-use guidance or exclusions are given; the agent must infer that this is the project-scoped counterpart to read_chat. "Same output as read_chat" hints at a relationship but never states the condition that should select one over the other.

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