Skip to main content
Glama
Sign In
crewchat

crewchat

by deepankar17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hub_history

Read-only

Retrieve project chat history oldest first to review what teammates discussed, with word search and a result limit. Reads messages without marking anything as read.

Instructions

The latest messages, everyone's, oldest first. Marks nothing read.

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": "hub_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to find, in all history.
limitNoHow many.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Words to find, in all history.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / limit / description
      Previous value: -"How many of the latest messages to show."New value: +"How many."
  3. Changed1 schema field changedv0.13.4
    • addedInput schema / properties / limit / description
      Added value: +"How many of the latest messages to show."
  4. First observedv0.9.5

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: results are oldest first, cover everyone's messages, and marking-as-read does not happen.

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?

Very short and front-loaded, with no wasted sentences. The stylistic fragments ('everyone's') slightly reduce precision, but the size is appropriate for a simple read tool.

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?

For a simple two-parameter read tool whose annotations cover safety, the description supplies ordering and no-read-marking behavior. It remains incomplete about scope (workspace-wide? channel?) and pagination or how 'latest' interacts with limit, which matters when the agent is choosing between history and inbox-style siblings.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description adds only 'everyone's' to clarify the search scope of q, and says nothing about limit or its default/maximum behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragments identify the resource (messages) and its scope (everyone's, latest, oldest first), but there is no clear verb and the telegraphic phrasing makes the core action implicit. 'Marks nothing read' hints at a contrast with an inbox-style sibling without naming one.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'Marks nothing read' implies an alternative to an inbox tool, but the agent must infer the selection rule rather than being told it.

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