Skip to main content
Glama

DATA/AGENT FOUNDRY

by io.github.Reztek-creator
OverviewDiscussionsAdmin

foundry_products

Free public discovery. Use {"view":"tasks","task":"exact_historical_evidence","subject":"postgresql"} to choose by historical task and held output, or {"view":"summary","limit":64} for the short offer index. Read {"product_id":""} alone for the public contract before advertised selectors or a quote. Omitting view/product_id preserves the full catalogue, default3 and limit1..64/next_cursor. Zero task cards is not zero vulnerabilities; a summary or schema enum is not MATCH or current applicability.

Input Schema

NameRequiredDescriptionDefault
taskNo
viewNo
limitNo
cursorNo
subjectNo
product_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / allOf
      Previous value: -[
-  {
-    "not": {
-      "required": [
-        "product_id",
-        "view"
-      ]
-    }
-  },
-  {
-    "not": {
-      "required": [
-        "product_id",
-        "limit"
-      ]
-    }
-  },
-  {
-    "not": {
-      "required": [
-        "product_id",
-        "cursor"
-      ]
-    }
-  },
-  {
-    "if": {
-      "not": {
-        "required": [
-          "product_id"
-        ]
-      }
-    },
-    "then": {
-      "properties": {
-        "limit": {
-          "default": 3
-        }
-      }
-    }
-  }
-]New value: +[
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "view"
+      ]
+    }
+  },
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "limit"
+      ]
+    }
+  },
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "cursor"
+      ]
+    }
+  },
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "task"
+      ]
+    }
+  },
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "subject"
+      ]
+    }
+  },
+  {
+    "if": {
+      "not": {
+        "required": [
+          "product_id"
+        ]
+      }
+    },
+    "then": {
+      "properties": {
+        "limit": {
+          "default": 3
+        }
+      }
+    }
+  },
+  {
+    "if": {
+      "required": [
+        "task"
+      ]
+    },
+    "then": {
+      "properties": {
+        "view": {
+          "const": "tasks"
+        }
+      },
+      "required": [
+        "view"
+      ]
+    }
+  },
+  {
+    "if": {
+      "required": [
+        "subject"
+      ]
+    },
+    "then": {
+      "properties": {
+        "view": {
+          "const": "tasks"
+        }
+      },
+      "required": [
+        "view"
+      ]
+    }
+  }
+]
    • addedInput schema / properties / subject
      Added value: +{
+  "enum": [
+    "apache_httpd",
+    "cert_fr",
+    "cisa_kev",
+    "cpython",
+    "go",
+    "multi_source_cve",
+    "postgresql"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "enum": [
+    "correction_group_dossier",
+    "declared_version_conditions",
+    "exact_historical_evidence",
+    "historical_comparison",
+    "historical_support_end"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / view / enum
      Previous value: -[
-  "summary"
-]New value: +[
+  "summary",
+  "tasks"
+]
  2. Changed4 schema fields changed
    • addedInput schema / allOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "view"
+      ]
+    }
+  },
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "limit"
+      ]
+    }
+  },
+  {
+    "not": {
+      "required": [
+        "product_id",
+        "cursor"
+      ]
+    }
+  },
+  {
+    "if": {
+      "not": {
+        "required": [
+          "product_id"
+        ]
+      }
+    },
+    "then": {
+      "properties": {
+        "limit": {
+          "default": 3
+        }
+      }
+    }
+  }
+]
    • removedInput schema / properties / limit / default
      Removed value: -3
    • addedInput schema / properties / product_id
      Added value: +{
+  "maxLength": 160,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "enum": [
+    "summary"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does add useful context: free public discovery, default limit, cursor pagination, product_id-only reads, and cautions that zero task cards is not zero vulnerabilities. However, it does not clearly state return format, authentication/rate-limit behavior, or explicitly declare read-only semantics.

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?

The description is dense but front-loaded with the core discovery purpose and examples, and the caveats at the end are meaningful. It could be clearer structurally, but there is little wasted text.

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?

For a tool with six optional parameters, complex allOf constraints, no annotations, and no output schema, the description covers the main usage modes and important caveats. It remains incomplete because it does not explain return values or fully document the enum and constraint semantics an agent would need for confident invocation.

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 description coverage is 0%, so the description must compensate. It partially does by explaining view modes, product_id-only usage, limit defaults/ranges, cursor continuation, and examples for task and subject, but it does not explain all task enum values or all combination constraints encoded in the schema.

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?

The description frames the tool as free public product discovery and uses examples to show catalogue, summary, task, and single-product contract retrieval. The purpose is clear from the modes and examples, though it does not explicitly name sibling tools or state a clean verb+resource phrase like 'list products'.

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?

It gives concrete mode-selection guidance: tasks view for historical task/output, summary view for the offer index, product_id alone for the public contract, and omitted selectors for the full catalogue. It also positions the tool before selectors or a quote, but does not explicitly name sibling alternatives or state when not to use it.

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

All DATA/AGENT FOUNDRY toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources