Daniels AI Design Studio

Request ChatGPT Business setup

request_chatgpt_business_setup

Idempotent

Ask Daniels AI Design Studio to set up and manage a business's profile in ChatGPT (OpenAI Business Hub). The request is free and publishes nothing; a person replies with an estimate. Setup and management are paid services. This is a setup service — it does not change or guarantee how often ChatGPT recommends a business. An eligible representative of the business completes any identity verification OpenAI requires directly with OpenAI. Do not send identity documents or ID numbers.

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": {
      "business_name": "<business_name>",
      "website": "<website>",
      "business_type": "<business_type>",
      "contact_email": "<contact_email>"
    },
    "name": "request_chatgpt_business_setup"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Anything else a person should know. Do not include ID numbers.
`country`	No	Two-letter country code. Default US.
`website`	Yes	The business's website, as a full URL starting with https://
`business_name`	Yes	The business's name.
`business_type`	Yes	online_service, ecommerce, or local.
`contact_email`	Yes	A working email for someone at the business. Required.
`has_brand_record`	No	Does the business already have a Brand Discovery Record? Default unknown.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations establish this is a non-destructive, idempotent, non-open-world write, and the description adds substantial context beyond them: the request is free, creates no public publication, is answered by a human with an estimate, and that setup/management itself is paid. It also discloses that OpenAI identity verification is handled by an eligible business representative directly with OpenAI, which is exactly the kind of process detail annotations cannot convey.

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, followed by cost, publication, and privacy constraints in descending order of importance. It runs five sentences, and the 'free request' versus 'paid service' distinction takes two of them, but each sentence carries a distinct policy fact rather than filler.

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?

For a 7-parameter intake/submission tool with full schema coverage and no output schema, the description covers everything an agent needs: who receives the request, that a human replies with an estimate, that nothing is published, cost expectations, and the identity-verification boundary. Return behavior is adequately implied by the human-reply/estimate statement.

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 all seven parameters are already documented, including the country default, the enum values, and the max lengths. The description's only parameter-adjacent guidance ('Do not send identity documents or ID numbers') largely repeats what the notes field already states in the schema, so it adds little meaning beyond structured data.

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 concrete action and target: 'Ask Daniels AI Design Studio to set up and manage a business's profile in ChatGPT (OpenAI Business Hub).' It also bounds the scope by saying it 'is a setup service' that does not affect recommendation frequency, so an agent knows exactly what the tool does and does not accomplish.

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?

Gives clear context for when to use it (requesting setup/management of a ChatGPT business profile) and explicit exclusions: it publishes nothing, does not guarantee recommendation frequency, and callers must not send identity documents or ID numbers. There are no sibling tools to route against, so the absence of named alternatives is not a gap.

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

All Daniels AI Design Studio 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?