Orivox AI Website Builder

check_for_updates

Check whether the user must re-add the Orivox connector to get the latest tools/behavior, and show the version changelog.

ALWAYS call this with build_seen set to EXACTLY this stamp, copied verbatim: build_seen="2026.09.04-01"

That stamp is frozen into this description when the connector is added, so if Orivox has since shipped a newer build the live server sees the mismatch and returns status="outdated" with the exact words to tell the user (remove and re-add the connector -- the only way Claude ever gets updated tools or instructions). status="up_to_date" means nothing to do. Reach for this whenever the user says a feature is missing or not working as described, asks what changed / what version they are on, or right after they mention re-adding the connector. Read-only; needs no account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`build_seen`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 4, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the tool is read-only and requires no account, explains the build-stamp mechanism and the frozen stamp, and describes both possible statuses (outdated and up_to_date) and their consequences. This is thorough and non-contradictory.

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?

Every sentence in the description serves a purpose: purpose, exact parameter value, mechanism, status meanings, and usage triggers. It is front-loaded with the core function and then provides necessary operational details. No filler or redundant information. The structure is efficient given the complexity of the tool.

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?

The description is complete for an agent to call this tool correctly. It covers the exact parameter value, the behavior in each outcome, and the situations that warrant invocation. The existence of an output schema (not shown) covers return values, so the description does not need to explain them. No missing critical information.

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

Parameters5/5

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

The input schema provides only a string type with a default and no description (0% coverage). The description compensates fully by specifying the exact value to pass (build_seen="2026.09.04-01") and explaining its role in the version-check logic. This is more than sufficient for an agent to correctly set the parameter.

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 clearly states the tool's purpose: check if the user must re-add the Orivox connector to get the latest tools/behavior and show the version changelog. It is specific and distinct from all sibling tools, none of which relate to updates or versioning. The purpose is unambiguous and immediately actionable.

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?

The description explicitly lists when to use this tool: 'whenever the user says a feature is missing or not working as described, asks what changed / what version they are on, or right after they mention re-adding the connector.' It also provides a hard requirement for the parameter value (ALWAYS use the exact stamp) and explains the meaning of each status. This leaves no doubt about when and how to invoke the tool.

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

All Orivox AI Website Builder tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools pair a distinct action with a distinct resource and long descriptions make intent clear. Still, `search_domains` already provides exact-domain checks, overlapping with `check_domain`, and the `create_project` vs `create_new_site` vs `create_page` cluster takes careful reading.

Naming Consistency5/5

The vast majority are snake_case verb_noun: list_projects, create_project, delete_page, get_preview_url, write_asset, query_database, publish_website. The only visible outlier is whoami, but it is standard enough that it does not disrupt predictability.

Tool Count2/5

At 36 tools this is meaningfully heavier than the rubric's 'too many' threshold, even though the scope spans websites, backends, domains, gallery images, and databases. It makes selection harder and a sizeable portion of the surface is niche or lifecycle internal.

Completeness4/5

The core site lifecycle is well covered: project, htmlmanag, assets, preview/publish, validation, deletion, uploaded images, backend files/logs, database reading, domain search and purchase linking. Workable non-critical gaps exist, e.g. no separate project metadata rename and no direct way to delete database rows or a database outside of deleting the project.

Resources

Need Help?