Static and WordPress Data Tools
Static Data returns administrator-authored JSON. WordPress Option returns the complete value from get_option() for the configured key.
Static Data stores an administrator-authored JSON value with the tool. A WordPress Option tool instead reads the complete current value of one option key at execution time. Both are “read-only” from the tool’s perspective, but whatever they return becomes model context and may be shown to the visitor, so disclosure review is essential.
First, choose static data or wordpress option. The useful result comes later when you enable only after data-owner approval, because configuration values matter only when their effect can be seen in retrieval, a generated reply, visitor access, or the connected service.
What this feature does and when to use it
Section titled “What this feature does and when to use it”Use Static Data for small controlled facts and WordPress Option only for a deliberately reviewed, nonsecret option.
Use this feature in the following situations:
- You need a small, stable set of public facts in a predictable structured format.
- You have a specifically reviewed nonsecret WordPress option that must be read at request time.
- You are testing how the assistant uses structured data without creating an external side effect.
Where to find it
Section titled “Where to find it”Before you begin
Section titled “Before you begin”- SmartSite Assistant is installed and activated.
- You are signed in with an account that can manage WordPress options.
Set it up step by step
Section titled “Set it up step by step”- Choose Static Data or WordPress Option.
- Complete common tool identity, description, assignment, and parameters.
- For Static Data, use the visual builder or valid raw JSON.
- For WordPress Option, enter the exact option key and inspect that option outside the assistant first.
- Save disabled and run a safe test.
- Verify the returned shape contains no secrets or unnecessary data.
- Enable only after data-owner approval.
Fields, controls, and important values
Section titled “Fields, controls, and important values”These controls decide what extra data can be placed into the model’s context. Static data is useful for small facts that change rarely; WordPress option data can expose live configuration. The AI may repeat anything the tool returns, so include only fields that genuinely improve the answer and never point an option tool at a value containing secrets or unrelated internal data.
| Field, control, or status | What SmartSite Assistant does with it | How to use it and why it matters |
|---|---|---|
| Static JSON builder | Builds structured static data; raw mode must be valid JSON. | Keep the tool associated with “Static JSON builder” disabled while checking valid, missing, malformed, and repeated inputs. Enable it only when the model description is narrow and the complete result cannot reveal or change anything beyond the approved purpose. |
| Option key | Passed to get_option(); the entire stored value is returned. | Enter “Option key” exactly as its source system provides it. This reference points the workflow at a particular resource; it does not improve AI reasoning, and the wrong value can quietly target the wrong account or stored record. |
| Tool result | Becomes context the model may include in its response. | Changing “Tool result” can alter capability, wording, speed, cost, or language, but it cannot fill gaps in the knowledge base. Compare the same realistic prompts before deciding that a model or translation choice is an improvement. |
| Enabled | Keeps an unreviewed data source unavailable to runtime. | “Enabled” controls whether this part of the workflow runs or appears. Its effect on responses depends on the feature—some switches change available knowledge or tools, while others only change presentation or protection—so perform the page-specific test. |
How to confirm it is working
Section titled “How to confirm it is working”After saving Static and WordPress Data Tools, repeat the final test with clean context. That distinction matters because WordPress can store a valid value even when remote processing, access rules, caching, or delivery prevents it from influencing the real experience.
Practical example
Section titled “Practical example”Use Static Data for public branch phone numbers rather than exposing a large plugin option array.
Recommended practice
Section titled “Recommended practice”- Change one part of Static and WordPress Data Tools at a time and keep a short record of the previous value and test result.
- Use synthetic arguments and inspect the complete raw result before letting the model call the tool in visitor conversations.
Important warnings
Section titled “Important warnings”Common problems and focused checks
Section titled “Common problems and focused checks”| Problem | What to check and what to do next |
|---|---|
| Static data will not save. | Validate the raw value as JSON and correct quotes, commas, and brackets. |
| Option result is empty. | Confirm the exact option key and whether the site stores the value in a different scope or format. |
| Static and WordPress Data Tools is missing or does not match this guide. | Confirm the plugin is active and the account can manage WordPress options. Keep the tool disabled while comparing its schema, arguments, implementation result, and any side effect. |
| A change on Static and WordPress Data Tools does not produce the expected result. | Keep the exact notice and test case, then review the browser console and WordPress/PHP log. Keep the tool disabled while comparing its schema, arguments, implementation result, and any side effect. |
Screen reference
Section titled “Screen reference”- Capture
- Show a Static Data tool with fictional public contact JSON in the visual builder and Enabled off.
- Show
- Tool type, JSON builder/raw toggle, safe sample fields, test action, Enabled
- Viewport
- Desktop, 1440 × 900
- Annotate
- Use numbered callouts only for controls referenced in the procedure.
- Redact
- OpenAI keys, tokens, secrets, personal information, private URLs, IP addresses, and conversation text