Skip to main content
Glama
Sign In

Ginta

by app.ginta
OverviewDiscussionsAdmin

Read the site's messages

get_messages
Read-onlyIdempotent

Use when the user asks for their messages, enquiries, orders or bookings: what visitors sent through the site's forms and Parts (shop orders and questions, quote requests, bookings, event sign-ups), newest first, as in Ginta's Messages. Visitors' emails, phone numbers and addresses are masked; get_message shows one message in full. Marking them read or deleting a form message: manage_site. Acting on an order, booking or sign-up: manage_module.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 50).
site_idYesThe site id: the first part of the site URL, e.g. "bella-roma" for https://bella-roma.ginta.page (see list_sites).

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).
totalYesAll messages and Part entries of the site.
site_idYesThe site id.
submissionsYesMessages, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / submissions / items / properties / kind / description
      Previous value: -"message = a form message; order/question = the Shop, quote = Quote requests, booking = Bookings, signup = Events."New value: +"message = a form message; order/question = the Shop, quote = Quote requests, booking = Bookings, signup = Events, review = Reviews (waiting for approval)."
    • changedOutput schema / properties / submissions / items / properties / kind / enum
      Previous value: -[
-  "message",
-  "order",
-  "question",
-  "quote",
-  "booking",
-  "signup"
-]New value: +[
+  "message",
+  "order",
+  "question",
+  "quote",
+  "booking",
+  "signup",
+  "review"
+]
  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"
+}
    • changedOutput schema / required
      Previous value: -[
-  "site_id",
-  "total",
-  "submissions"
-]New value: +[
+  "site_id",
+  "total",
+  "submissions",
+  "text"
+]
  3. Changed3 schema fields changed
    • addedOutput schema / properties / submissions / items / properties / fields / description
      Added value: +"What was sent (labels → values); emails, phone numbers and addresses masked."
    • changedOutput schema / properties / submissions / items / properties / part / description
      Previous value: -"The Part the entry lives in (a manage_module module id)."New value: +"The Part the entry lives in (its module id)."
    • changedOutput schema / properties / submissions / items / properties / status / description
      Previous value: -"paid, done, cancelled, refunded, quoted, won, lost, waitlist or not_paid; absent = new or confirmed."New value: +"paid, done, cancelled, refunded, quoted, won, lost, waitlist, not_paid, or whatsapp (an order sent on WhatsApp, not paid); absent = new or confirmed."
  4. Changed7 schema fields changed
    • addedOutput schema / properties / submissions / items / properties / kind
      Added value: +{
+  "description": "message = a form message; order/question = the Shop, quote = Quote requests, booking = Bookings, signup = Events.",
+  "enum": [
+    "message",
+    "order",
+    "question",
+    "quote",
+    "booking",
+    "signup"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / submissions / items / properties / link
      Added value: +{
+  "description": "Where the owner opens it in Ginta (path on ginta.app).",
+  "type": "string"
+}
    • addedOutput schema / properties / submissions / items / properties / number
      Added value: +{
+  "description": "Order or quote request number.",
+  "type": "number"
+}
    • addedOutput schema / properties / submissions / items / properties / part
      Added value: +{
+  "description": "The Part the entry lives in (a manage_module module id).",
+  "type": "string"
+}
    • addedOutput schema / properties / submissions / items / properties / status
      Added value: +{
+  "description": "paid, done, cancelled, refunded, quoted, won, lost, waitlist or not_paid; absent = new or confirmed.",
+  "type": "string"
+}
    • changedOutput schema / properties / submissions / items / required
      Previous value: -[
-  "id",
-  "received_at",
-  "unread",
-  "fields"
-]New value: +[
+  "id",
+  "kind",
+  "received_at",
+  "unread",
+  "fields"
+]
    • changedOutput schema / properties / total / description
      Previous value: -"All messages of the site."New value: +"All messages and Part entries of the site."
  5. Changed2 schema fields changed
    • addedOutput schema / properties / submissions / items / properties / emailed
      Added value: +{
+  "const": false,
+  "description": "Present when the email about it didn't go out (it's still saved).",
+  "type": "boolean"
+}
    • addedOutput schema / properties / submissions / items / properties / not_emailed
      Added value: +{
+  "description": "Why: the month's emails used up, the website's form emails for today, or sending failed.",
+  "enum": [
+    "month",
+    "day",
+    "failed"
+  ],
+  "type": "string"
+}
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description still adds real behavioral context the annotations cannot: results are ordered newest first and visitor emails, phone numbers and addresses are masked, which materially affects how an agent should interpret and relay results. It stops short of describing pagination behavior or how the limit interacts with the newest-first ordering, which is the only notable gap.

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?

Front-loaded with the usage trigger, then behavior (ordering, masking), then sibling routing; no sentence is redundant. The long parenthetical enumerations and the reference to Ginta's Messages add slight density, but they carry genuine disambiguation value 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 two-parameter read tool with an output schema (so return shape needn't be explained) and full annotation coverage, the description supplies everything an agent needs: trigger conditions, scope, ordering, PII masking, and where to go for the full record or for mutations. Nothing material is left to inference.

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% and both parameters (site_id with a URL-derived example, limit with default 50 and a 1-200 bound) are fully documented in the schema itself. The description adds no parameter-level meaning beyond the schema — the ordering note describes results, not an input — so the baseline 3 applies.

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 (read the site's messages), enumerates the concrete content types it covers (shop orders, quote requests, bookings, event sign-ups) and explicitly distinguishes itself from get_message, manage_site and manage_module. An agent can identify exactly what comes back without opening the schema.

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?

Opens with an explicit trigger ("Use when the user asks for their messages, enquiries, orders or bookings") and names three alternatives with the conditions that select them: get_message for a single full message, manage_site for mark-read/delete, manage_module for acting on an order or booking. Both when-to-use and when-not-to-use are covered.

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