Skip to main content
Glama
Sign In

Ginta

by app.ginta
OverviewDiscussionsAdmin

Live parts: menu, bookings, shop, blog…

manage_module
Destructive

Use to set up or change the live parts the owner manages, without rewriting pages: menu, bookings, shop (catalog), blog, gallery, events, quote form, announcements, reviews and lists (collections), and the bookings, orders, sign-ups, quote requests and reviews they receive. Omit module to see the parts and what the plan includes; action "help" lists a module's actions and fields (no site_id needed). Some actions email the business's customers (a cancelled or moved booking, an order update).

Input Schema

NameRequiredDescriptionDefault
dataNoThe action's fields (see help), e.g. for menu setup {"sections": [...]}. Unknown fields are refused.
actionNoWhat to do, e.g. "setup", "get", "list", "save_item"; "help" lists the actions and their fields.
moduleNoWhich module (omit to list them all).
site_idNoThe site id (see list_sites). Not needed for action "help" or to list the modules.

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in words, the same as the text content: read it (for get_guide the whole guide, for get_site the files' contents).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / module / enum
      Previous value: -[
-  "collections",
-  "announcements",
-  "menu",
-  "gallery",
-  "blog",
-  "bookings",
-  "catalog",
-  "quote",
-  "events"
-]New value: +[
+  "collections",
+  "announcements",
+  "menu",
+  "gallery",
+  "blog",
+  "bookings",
+  "catalog",
+  "quote",
+  "events",
+  "reviews"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / text
      Added value: +{
+  "description": "The answer in words, the same as the text content: read it (for get_guide the whole guide, for get_site the files' contents).",
+  "type": "string"
+}
    • addedOutput schema / required
      Added value: +[
+  "text"
+]
  3. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"What to do, e.g. \"setup\", \"get\", \"list\", \"save_item\" (see above); \"help\" for the fields."New value: +"What to do, e.g. \"setup\", \"get\", \"list\", \"save_item\"; \"help\" lists the actions and their fields."
    • changedInput schema / properties / data / description
      Previous value: -"The action's fields (see help), e.g. for menu setup {\"sections\": [...]}."New value: +"The action's fields (see help), e.g. for menu setup {\"sections\": [...]}. Unknown fields are refused."
    • changedInput schema / properties / module / description
      Previous value: -"Which module (omit to list them all for this site)."New value: +"Which module (omit to list them all)."
    • changedInput schema / properties / site_id / description
      Previous value: -"The site id: the first part of the site URL, e.g. \"bella-roma\" for https://bella-roma.ginta.page (see list_sites)."New value: +"The site id (see list_sites). Not needed for action \"help\" or to list the modules."
    • removedInput schema / required
      Removed value: -[
-  "site_id"
-]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the destructiveHint/openWorldHint annotations, the description discloses a genuinely important side effect: some actions email the business's customers (cancelled or moved bookings, order updates). That is behavior an agent cannot infer from annotations or schema. It stops short of describing what data is destroyed by destructive actions, which is the biggest residual gap given destructiveHint=true.

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, followed by the discovery path and then the side-effect warning. The long module enumeration is dense but earns its place by implying the enum's scope; a reader can scan the first sentence and act.

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

Completeness3/5

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

Output schema exists, so return values need no explanation, and the discovery flow plus email side effect are covered. For a destructive, non-idempotent, open-world dispatcher spanning ten modules, the description never says what deletion or overwriting means here, which is a real gap. Adequate for navigation, thin on risk.

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 coverage is 100%, so all four parameters already carry descriptions including the omit-module and help/no-site_id behaviors. The description restates those rules and adds only the detail that the module listing includes plan inclusions; it adds little on `data` or `action` values beyond pointing at "help".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: "set up or change the live parts the owner manages," then enumerates the concrete modules (menu, bookings, shop, blog, gallery, events, quote, announcements, reviews, collections). The scope is distinguishable from page-editing siblings via "without rewriting pages." However, the actions themselves remain opaque (only examples like setup/get/list/save_item appear in the schema, not the description).

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 a clear discovery workflow: omit `module` to see the parts and plan inclusions, and use action "help" to list a module's actions and fields. It does not name an alternative sibling (e.g. manage_site, update_site) or state when-not to use this dispatcher, so routing to it versus page-level tools is left implicit.

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

All Ginta toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources