Skip to main content
Glama

List AI Cofounder Messages

list_ai_cofounder_messages
Read-only

List messages for an AI Cofounder chat. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "chatId": "<chatId>"
    },
    "name": "list_ai_cofounder_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdYesChat ID, from a chat listing.
batchSizeNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
previousObjectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / chatId / description
      Added value: +"Chat ID, from a chat listing."
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this as a non-destructive, read-only, closed-world operation. The description adds genuinely useful context beyond them—business-tier gating and grace-period/resubscribe messaging—but says nothing about pagination behavior or how results are ordered, which matters for a list tool with batchSize and previousObjectId parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, which is good. However, the permission preamble is redundant—'check business permissions' is immediately restated as 'Call check_business_tool_access before collecting inputs'—and the gating instruction crowds out information about the listing itself.

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

Completeness4/5

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

For a read-only list tool with no output schema, the permission and eligibility rules are covered thoroughly, which is the main risk area. The gap is the undefined pagination parameters and absent description of result shape or ordering, so it falls short of fully 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 only 50%: chatId and communityId are documented in the schema, while batchSize and previousObjectId carry no description anywhere. The prose adds no meaning to any of the four parameters, leaving the pagination contract entirely unexplained.

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 first sentence gives a specific verb and resource: 'List messages for an AI Cofounder chat.' It is immediately clear what the tool returns, but it does not distinguish itself from siblings such as list_ai_cofounder_chats or list_magic_reach_messages, so an agent gets no help disambiguating between the listing tools.

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

Usage Guidelines4/5

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

Usage is framed through explicit preconditions: call check_business_tool_access before collecting inputs, FREE businesses are excluded, and never proceed when access is blocked. That is a strong when-not rule, but no alternative tool is named for the excluded or blocked cases, which keeps it below a 5.

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