Onsomble

Create Prompt

create_prompt

Create a new active question with text, category and optional assignments. Omitted arrays start empty. Active matching text is refused. Matching retired text returns retiredMatches with prompt=null and performs no write: choose reactivate_prompt to keep history, or repeat create_prompt with every returned ID in acknowledgedRetiredPromptIds to explicitly create a fresh identity with separate history. Matching trims/collapses whitespace, ignores case and trailing .?!; it is not fuzzy. Stale acknowledgements are rejected. Use get_scan_config for current strategy definitions and list_prompts for saved questions. Returns the complete saved prompt with the same fields as list_prompts, retiredMatches (empty after success), and working scanConfig. Does not launch a Scan.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Free-form labels. Omission preserves on edit/restoration; null or [] clears.
`text`	Yes
`siteId`	Yes	Site or Topic ID from list_sites_and_topics.
`regions`	No	Exact prompt-selectable refs from list_regions. Omission preserves on edit/restoration; null or [] inherits scan defaults, then Global if defaults are empty.
`category`	Yes
`personas`	No	Audience definition IDs or names from get_scan_config.personas. Include relevant audiences in the creation call. Omission preserves on edit/restoration; null or [] clears.
`products`	No	Strategy product/service IDs or names from get_scan_config.products. Optional for Topics. Omission preserves on edit/restoration; null or [] clears.
`journeyStages`	No	Definition IDs or names from get_scan_config.journeyStages. First is primary; separate from category. Optional for Topics. Omission preserves on edit/restoration; null or [] clears both stages and primary.
`acknowledgedRetiredPromptIds`	No	Explicit fresh-create acknowledgement of every returned retired match ID. Omit until the choices have been reviewed.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`prompt`	Yes
`summary`	Yes
`scanConfig`	Yes
`retiredMatches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the deduplication rules (whitespace trimming, case-insensitivity, trailing .?! ignored, not fuzzy), the no-write behavior on retired matches, stale-acknowledgement rejection, and that it does not launch a Scan.

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 purpose is front-loaded and every sentence conveys distinct behavioral or routing information. It reads as a dense block, but given the deduplication and reactivation workflow, the length is largely justified.

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?

Despite an output schema existing, the description still summarizes the return payload (saved prompt, empty retiredMatches on success, working scanConfig) and clarifies the side-effect boundary ('Does not launch a Scan'). Nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 78% and the schema documents most parameters (tags, siteId, regions, personas, products, journeyStages). The description adds real meaning for acknowledgedRetiredPromptIds by explaining it carries every returned retired ID to force a fresh create.

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 new active question') with its key fields (text, category, optional assignments). It clearly distinguishes itself from reactivate_prompt and update_prompt by framing the operation as creating a fresh identity.

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?

Explicitly routes the agent: active-matching text is refused, retired-matching text offers a choice between reactivate_prompt (keep history) or repeating create_prompt with acknowledgedRetiredPromptIds (fresh identity). It also points to get_scan_config and list_prompts for supporting data.

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

All Onsomble 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?