Nas.com

Create Session

create_session

Create a one-on-one session product for a community managed by the authenticated Nas.com user. 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>",
      "title": "<title>",
      "durationIntervalInMinutes": "<durationIntervalInMinutes>",
      "location": "<location>",
      "status": "<status>",
      "createdBy": "<createdBy>",
      "availability": "<availability>",
      "timezoneChosenForAvailability": "<timezoneChosenForAvailability>",
      "hostInfo": "<hostInfo>",
      "minimumNoticeInDaysForBooking": "<minimumNoticeInDaysForBooking>",
      "unAvailableDates": "<unAvailableDates>"
    },
    "name": "create_session"
  }
}

Input Schema

Name	Required	Description
`index`	No
`title`	Yes	Title shown to members.
`access`	No
`amount`	No	Price amount in the business currency.
`status`	Yes	Status value; use one of the allowed values in this schema.
`currency`	No	Three-letter ISO 4217 currency code, for example USD.
`hostInfo`	Yes	Host details shown to members who book the session.
`location`	Yes	Where the session takes place (online link or address details).
`createdBy`	Yes	User ID of the business manager creating the session.
`minAmount`	No
`priceType`	No
`thumbnail`	No
`communityId`	Yes	Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
`description`	No	Description shown to members.
`availability`	Yes	Weekly hours when the session can be booked.
`resourceSlug`	No
`tieredPrices`	No	Price tiers to save for the business.
`discountsToAdd`	No
`coverMediaItems`	No	Cover images or videos for the product.
`suggestedAmount`	No
`unAvailableDates`	Yes	Dates when the session cannot be booked.
`discountsToRemove`	No
`templateLibraryId`	No
`descriptionContent`	No	Rich-text product description.
`discountsToDisable`	No
`richTextMediaFiles`	No
`newDiscountsToApply`	No
`stopAcceptingBookings`	No
`duplicateFromSessionId`	No
`durationIntervalInMinutes`	Yes	Session length in minutes.
`applicationConfigDataFields`	No	Questions to ask applicants.
`minimumNoticeInDaysForBooking`	Yes	Minimum number of days of notice required before a booking.
`timezoneChosenForAvailability`	Yes	IANA time zone that the availability hours are written in.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedNov 10, 2026

addedInput schema / properties / amount / description

Added value: +"Price amount in the business currency."

addedInput schema / properties / applicationConfigDataFields / description
```
Added value: +"Questions to ask applicants."
```

addedInput schema / properties / availability / description

Added value: +"Weekly hours when the session can be booked."

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 / coverMediaItems / description
```
Added value: +"Cover images or videos for the product."
```

addedInput schema / properties / createdBy / description

Added value: +"User ID of the business manager creating the session."

addedInput schema / properties / currency / description

Added value: +"Three-letter ISO 4217 currency code, for example USD."

addedInput schema / properties / description / description
```
Added value: +"Description shown to members."
```
addedInput schema / properties / descriptionContent / description
```
Added value: +"Rich-text product description."
```
addedInput schema / properties / durationIntervalInMinutes / description
```
Added value: +"Session length in minutes."
```

addedInput schema / properties / hostInfo / description

Added value: +"Host details shown to members who book the session."

addedInput schema / properties / location / description

Added value: +"Where the session takes place (online link or address details)."

addedInput schema / properties / minimumNoticeInDaysForBooking / description

Added value: +"Minimum number of days of notice required before a booking."

addedInput schema / properties / status / description

Added value: +"Status value; use one of the allowed values in this schema."

addedInput schema / properties / tieredPrices / description
```
Added value: +"Price tiers to save for the business."
```

addedInput schema / properties / timezoneChosenForAvailability / description

Added value: +"IANA time zone that the availability hours are written in."

addedInput schema / properties / title / description
```
Added value: +"Title shown to members."
```
addedInput schema / properties / unAvailableDates / description
```
Added value: +"Dates when the session cannot be booked."
```

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds genuinely new behavior: tier-based entitlement blocking and a mandatory access-check flow with a grace-period warning. It still says nothing about what side effects creation produces, whether the session is Draft by default, or what happens on validation failure.

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?

Front-loaded with purpose, then the gating rules in logical order. It is slightly repetitive — 'check business permissions', 'FREE businesses cannot use this tool', 'Call check_business_tool_access', and 'never proceed when access is blocked' restate the same precondition twice — but no sentence is off-topic.

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

Completeness2/5

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

For a 33-parameter, 11-required, deeply nested creation tool with no output schema, the description covers only the access gate and none of the substantive input contract. An agent can correctly determine whether it may call the tool but not how to populate availability, hostInfo, pricing, or location correctly.

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 55% across 33 parameters, and the description adds no parameter meaning whatsoever — it never mentions required fields like availability, hostInfo, timezoneChosenForAvailability, or minimumNoticeInDaysForBooking. Numerous fields (priceType, tieredPrices, discountsToAdd, templateLibraryId, duplicateFromSessionId, stopAcceptingBookings) are undocumented in both places, leaving the agent to guess.

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

Purpose5/5

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

States a specific verb and resource: 'Create a one-on-one session product for a community'. The scope qualifier ('managed by the authenticated Nas.com user') makes it distinguishable from update_session, delete_session, and the publish/unpublish siblings without opening any schema.

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?

Gives explicit preconditions rather than vague context: call check_business_tool_access before collecting inputs, FREE businesses cannot use the tool regardless of feature rows, surface the grace-period warning and resubscribe link, and never proceed when access is blocked. It names the alternative tool to call and the condition that gates the action.

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.