Skip to main content
Glama
theonlytruebigmac

N-central MCP Server

create_service_org

Create a new service organization by providing the organization name and primary contact's first and last names.

Instructions

Create a new service organization. Required: contactFirstName, contactLastName, soName.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
soNameYesService organization name
contactFirstNameYesPrimary contact first name
contactLastNameYesPrimary contact last name
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, e.g. "US")
postalCodeNoPostal/ZIP code
Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's mention of 'Create' adds no new behavioral insight. The description does not disclose side effects, permissions needed, or what the response contains (e.g., created object ID).

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

Conciseness5/5

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

The description is a single sentence followed by a list of required parameters. It is extremely succinct with no unnecessary words or repetition, making it easy to scan and understand.

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?

Despite having 16 parameters and no output schema, the description omits crucial context such as what the tool returns after creation, whether the service org is immediately usable, or any prerequisites. The schema covers parameters well, but behavioral completeness is low.

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?

All 16 parameters have descriptions in the input schema (100% coverage), so the schema already explains each field. The description only names the required ones, providing no additional semantic meaning or usage context beyond what the schema offers.

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?

The description explicitly states 'Create a new service organization' which is a clear verb-resource pair that precisely identifies the tool's function. The tool name 'create_service_org' distinguishes it from other creation tools like 'create_customer' by specifying the entity type.

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

Usage Guidelines3/5

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

The description lists the three required parameters (soName, contactFirstName, contactLastName) which implies these are mandatory for use. However, it provides no guidance on when to use this tool versus alternatives such as 'create_customer' or how to decide based on context.

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