Skip to main content
Glama
theonlytruebigmac

N-central MCP Server

create_site

Create a new site for a customer using required contact first name, last name, and site name.

Instructions

Create a new site under a customer (PREVIEW endpoint — schema may change between N-central versions). Required: contactFirstName, contactLastName, siteName.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe customer ID this site belongs to
siteNameYesSite name
contactFirstNameYesPrimary contact first name
contactLastNameYesPrimary contact last name
licenseTypeNoLicense type
externalIdNoOptional external identifier
phoneNoMain phone number
contactTitleNoContact title
contactEmailNoContact email
contactPhoneNoContact phone
contactPhoneExtNoContact phone extension
contactDepartmentNoContact department
street1NoStreet address line 1
street2NoStreet address line 2
cityNoCity
stateProvNoState/Province
countryNoCountry (ISO 2-letter)
postalCodeNoPostal/ZIP code
Behavior3/5

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

Description adds the preview endpoint warning, providing useful behavioral context beyond annotations. However, it does not disclose error states, success response, or side effects beyond creation.

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?

Description is one sentence with a parenthetical, front-loading the purpose. However, missing customerId in required list slightly reduces clarity.

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?

With 18 parameters and no output schema, description does not explain return value, prerequisites, or what happens on success/failure. Incomplete for a creation tool.

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 coverage is 100%, so description adds minimal value. It repeats some required fields but incorrectly omits customerId. Baseline is 3.

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 description clearly states the verb 'create' and resource 'site under a customer'. It distinguishes from siblings like create_customer or create_device. However, it omits customerId from the listed required fields, which may cause minor confusion.

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 guidance on when to use this tool vs alternatives. Does not mention when not to use it or provide any context about prerequisites or edge cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theonlytruebigmac/n-central-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server