Skip to main content
Glama
Sign In

Fas

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fas Commodity Codes

fas_commodity_codes
Read-onlyIdempotent

Search agricultural commodity codes and names. Returns commodity IDs, descriptions, and categories. Use results with fas_production.

Input Schema

NameRequiredDescriptionDefault
searchNoSearch keyword (e.g., "soy", "wheat"). Optional.
categoryNoFilter by category: "Grains", "Oilseeds", "Meat", "Dairy", "Fiber", "Sugar", "Tropical" (optional)

Output Schema

NameRequiredDescriptionDefault
noteYesUsage guidance for commodity and country codes
totalYesTotal number of matching commodity codes
categoriesYesCommodities grouped by category
country_codesYesMapping of ISO 2-letter country codes to country names

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / country_codes / description
      Previous value: -"ISO 2-letter country codes and names"New value: +"Mapping of ISO 2-letter country codes to country names"
    • changedOutput schema / properties / note / description
      Previous value: -"Usage note for the codes"New value: +"Usage guidance for commodity and country codes"
    • changedOutput schema / properties / total / description
      Previous value: -"Total number of commodities matching filter"New value: +"Total number of matching commodity codes"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "categories": {
+      "additionalProperties": {
+        "items": {
+          "properties": {
+            "code": {
+              "description": "Commodity code",
+              "type": "string"
+            },
+            "name": {
+              "description": "Commodity name",
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "name"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "description": "Commodities grouped by category",
+      "type": "object"
+    },
+    "country_codes": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "ISO 2-letter country codes and names",
+      "type": "object"
+    },
+    "note": {
+      "description": "Usage note for the codes",
+      "type": "string"
+    },
+    "total": {
+      "description": "Total number of commodities matching filter",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "categories",
+    "country_codes",
+    "note"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "category": "Oilseeds",
+    "search": "soy"
+  },
+  {
+    "category": "Grains"
+  }
+]
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds the shape of the return (IDs, descriptions, categories) and the downstream pairing with fas_production, but says nothing about result limits, pagination, or empty-result behavior for a search endpoint.

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?

Three short sentences, front-loaded with the action and resource, then return shape, then the integration hint. Nothing is redundant or padded.

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

Completeness4/5

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

An output schema exists, so return values need not be explained; the description nonetheless sketches them. For a two-optional-param read-only search, this is nearly complete, with only matching/pagination behavior left implicit.

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 carry their own descriptions plus examples, so the schema does the heavy lifting. The description adds no syntax or matching semantics (e.g., substring vs exact, case sensitivity, how search and category combine).

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 (search) and resource (agricultural commodity codes) and names the concrete return fields (IDs, descriptions, categories). It does not explicitly contrast with any alternative search tool, but it does name the downstream companion fas_production.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The only guidance is the trailing 'Use results with fas_production,' which explains downstream flow rather than when to call this tool versus another. No when-not conditions or alternative tool routing are given.

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

All Fas 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