Conciergr

Sign up another business

start_new_business

Start a Conciergr signup for a NEW business (not the one this connection works on): a 30-day free trial with everything on, then SGD 89 a month with everything included, plus SGD 20 a month for each branch past the first. No invite code is needed. Ask for the new business's name customers know. Returns Stripe's page for the person to open and add their card; only they can enter it, and nothing is charged until the trial ends.

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": {
      "businessName": "<businessName>"
    },
    "name": "start_new_business"
  }
}

Input Schema

Name	Required	Description	Default
`businessName`	Yes	The new business's name, as customers know it, up to 80 characters.
`referredByOwner`	No	Whether another business owner told them about Conciergr, if they say.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond annotations, the description discloses the full commercial and interaction model: 30-day free trial, SGD 89/month plus branch pricing, Stripe-hosted card entry, and no charge until trial end. It also clarifies that only the customer can enter card details, which is important behavioral context for an open-world, non-read-only action.

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?

The description is front-loaded with the key distinction ('NEW business, not the one this connection works on') and remains readable despite including pricing details. Some pricing granularity is extra, but it likely helps the agent set expectations and does not obscure the core instructions.

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

Completeness5/5

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

With no output schema, the description appropriately explains what comes back: Stripe's page for the person to open and add their card. Combined with trial and billing context, it is complete enough for an agent to call this tool and explain next steps to the user.

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%, so both parameters are already fully documented. The description reinforces the businessName semantics by saying to ask for the name customers know, but it does not mention referredByOwner at all. Baseline 3 is appropriate because the schema carries the parameter burden.

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 states a specific action ('Start a Conciergr signup') and resource ('a NEW business') while explicitly excluding the current connection's business. This gives an agent a clear, unambiguous purpose that distinguishes it from sibling tools like mark_signed_up or open_billing.

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?

The description gives clear usage context: use this to sign up a brand-new business, not the one already connected, and notes that no invite code is required. It lacks an explicit named alternative for other signup-related flows, but the exclusion condition is strong enough for correct routing.

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

All Conciergr 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.

Resources

Need Help?