Nas.com

Send AI Cofounder Message

send_ai_cofounder_message

Send a signed message to 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>",
      "message": "<message>",
      "intentType": "<intentType>"
    },
    "name": "send_ai_cofounder_message"
  }
}

Input Schema

Name	Required	Description
`chatId`	Yes	Chat ID, from a chat listing.
`message`	Yes	Message text to send to AI Cofounder.
`platform`	No	Messaging channel; use one of the allowed values.
`timezone`	No	IANA time zone, for example Asia/Singapore.
`actionType`	No
`intentType`	Yes	Intent of the AI Cofounder message, as accepted by the AI Cofounder API.
`responseId`	No
`attachments`	No
`communityId`	Yes	Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
`templateObjectId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

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."

addedInput schema / properties / intentType / description

Added value: +"Intent of the AI Cofounder message, as accepted by the AI Cofounder API."

addedInput schema / properties / message / description

Added value: +"Message text to send to AI Cofounder."

addedInput schema / properties / platform / description

Added value: +"Messaging channel; use one of the allowed values."

addedInput schema / properties / timezone / description

Added value: +"IANA time zone, for example Asia/Singapore."

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare a non-read-only, non-destructive, closed-world mutation. The description adds real context beyond that: messages are signed, access is gated by business tier, FREE businesses are blocked independent of feature rows, and grace-period/resubscribe flows must be surfaced. It does not describe rate limits, side effects on the chat thread, or what a call returns when access is denied.

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?

Purpose is front-loaded in the first sentence and the gating rules follow in priority order. There is mild redundancy between 'check business permissions' and 'Call check_business_tool_access,' but every sentence carries an actionable constraint.

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 mutation tool with 10 parameters and no output schema, the access-control story is thorough but the message payload story is not. Nothing explains attachment constraints, the 2000-character message limit's implications, or what happens on a successful send. It is adequate on permissions, incomplete on the operation itself.

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 60% across 10 parameters, and the description adds no meaning to any of them. communityId, chatId, message, and intentType carry schema text, but platform, actionType, responseId, attachments, and templateObjectId are undocumented in both places, and 'platform' says 'use one of the allowed values' without any enum present. The description could have clarified required-versus-optional intent but does not.

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: 'Send a signed message to an AI Cofounder chat.' The resource ('AI Cofounder chat') distinguishes it from the magic-reach messaging siblings. It stops short of explicitly naming an alternative or contrast case, so it is clear but not fully differentiated.

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

Usage Guidelines5/5

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

Explicitly states prerequisites and exclusions: check business permissions before offering the action, FREE businesses cannot use it regardless of feature rows, call check_business_tool_access before collecting inputs, surface grace-period warnings and resubscribe links, and never proceed when access is blocked. This names the gate, the ordering, and the hard stop condition, which is exactly what an agent needs.

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

All Nas.com tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.