Skip to main content
Glama

Create AI Cofounder Chat

create_ai_cofounder_chat

Create a signed 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>",
      "message": "<message>"
    },
    "name": "create_ai_cofounder_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage text to send to AI Cofounder.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
    • addedInput schema / properties / message / description
      Added value: +"Message text to send to AI Cofounder."
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, non-open-world call; the description adds real behavioral context the agent would otherwise lack, namely that a business-level access gate exists, that FREE tier is excluded independent of feature rows, and that a warning flow must be shown. It does not state what a successful call returns (e.g., chat ID) or whether the chat is reusable, which keeps it short of a 5.

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?

The action is front-loaded in one sentence, which is good, but the remaining text restates the same access rule three times (check business permissions, call check_business_tool_access, never proceed when blocked). It is policy-dense rather than wasteful overall, yet it could be tightened without losing meaning.

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?

There is no output schema, so the description should say what a successful creation yields (a chat object, an ID to pass to send_ai_cofounder_message) and it does not. The access-gating side is covered thoroughly, but the agent is left guessing about the result and about how to continue the conversation afterward.

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% with only two required parameters, so the schema already fully documents message text and communityId (including the "never invent one" rule). The description contributes nothing about parameter values, formats, or constraints, so the baseline 3 applies.

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?

"Create a signed AI Cofounder chat" names a verb and a resource, so the action is identifiable, but "signed" is unexplained jargon and nothing distinguishes this from siblings like send_ai_cofounder_message or list_ai_cofounder_chats. The single purpose sentence is immediately buried under access-policy text, so the agent's understanding of what is actually created remains thin.

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?

Strong explicit preconditions: call check_business_tool_access before collecting inputs, FREE businesses cannot use it regardless of feature rows, surface any grace-period warning and verified resubscribe link, and never proceed when access is blocked. It does not compare against sibling tools for creating or messaging in a chat, but the when/when-not rules for this tool are unusually concrete.

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