Skip to main content
Glama
gura105

Operational Ontology

by gura105
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

traverse_order_products

Traverse the orderProducts many-to-many link from a retrieved Order or Product instance, inferring direction from source type or validating an explicit forward/reverse choice.

Instructions

Traverse the Order → Product link "orderProducts" (many-to-many). Pass an instance returned by get or search; its properties are a snapshot, not authority. Direction is inferred from source.type; an explicit direction must agree.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • removedInput schema / properties / direction / default
      Removed value: -"forward"
    • removedInput schema / properties / pk
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / source
      Added value: +{
+  "properties": {
+    "pk": {
+      "type": "string"
+    },
+    "properties": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": {
+      "enum": [
+        "Order",
+        "Product"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "type",
+    "pk",
+    "properties"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "pk"
-]New value: +[
+  "source"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does add real behavior: the passed properties are a snapshot, not authoritative, and direction is inferred from source.type with explicit direction required to agree. It still omits whether the operation is read-only, what it returns, and pagination/limits for a many-to-many traversal.

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?

Three compact sentences, front-loaded with the relationship and its cardinality. Slightly dense and abbreviation-heavy, but no sentence is wasted.

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?

The input side is well covered, but with no output schema and no statement of what a traversal returns (related Product or Order instances, counts, pagination), the description leaves the agent guessing about results for a nested, many-to-many operation.

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 0%, so the description must compensate, and it does: 'source' must be an instance from get/search and its properties are snapshot-only, while 'direction' is normally derived from source.type and must agree if supplied. It adds meaning well beyond the bare enum, though it doesn't explain direction values themselves.

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?

Names a specific verb (traverse), the exact relationship ('orderProducts', many-to-many) and its endpoints, which cleanly separates it from siblings like traverse_customer_orders and traverse_order_notes. An agent can identify the operation 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the prerequisite clearly ('Pass an instance returned by get or search'), which tells the agent what to feed it. It does not state when to prefer this over alternatives such as search_product, but the traversal-vs-search distinction is reasonably implied by the tool name and the snapshot caveat.

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

Deploy Server

Other Tools