Skip to main content
Glama

SuppCo

by co.supp
OverviewDiscussionsAdmin

Get product info

suppco_get_product_info
Read-onlyIdempotent

Look up detailed information (composition, ingredients, price, format, servings) for one or more specific products by UUID, slug, or name. Use for "tell me about " or to hydrate products you only have ids for (e.g. from the user's stack). Accepts names when you don't have an id yet. For TrustScore rationale, certifications, or testing, call suppco_get_product_trust_score instead.

Input Schema

NameRequiredDescriptionDefault
productsYesOne or more product identifiers (max 5): an array of strings, or one string separated by ' | '. Each can be a UUID, slug, or product name. Prefer the ids you already have from a previous product result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / products / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / products / description
      Previous value: -"One or more product identifiers separated by ' | ' (max 5). Each can be a UUID, slug, or product name. Prefer slugs or UUIDs when available. Examples: 'thorne-vitamin-d-k2' (single slug), 'Thorne Magnesium | Pure Encapsulations Vitamin D' (multiple by name)"New value: +"One or more product identifiers (max 5): an array of strings, or one string separated by ' | '. Each can be a UUID, slug, or product name. Prefer the ids you already have from a previous product result."
    • removedInput schema / properties / products / type
      Removed value: -"string"
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is fully covered without the description. The description adds the useful behavioral note that names are accepted when no id exists, implying fuzzy resolution, but says nothing about ambiguity, failures for unmatched names, auth, or rate limits. Adequate but not rich.

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 tight sentences, front-loaded with purpose and returned fields before the alternative-tool routing. No filler phrases and nothing redundant with the schema beyond a brief identifier recap.

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?

With no output schema present, the description compensates by naming the returned fields, and it covers identifier formats, batching, and sibling routing for a one-parameter read tool. An agent has everything needed to call this correctly.

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 100% and the single parameter is fully documented there, including the max-5 limit, the ' | ' string form, and the preference for previously obtained ids. The description restates rather than extends this, 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 (look up) and resource (product info) and enumerates the returned fields (composition, ingredients, price, format, servings) plus the accepted identifier types (UUID, slug, name). It explicitly names the sibling it is not for trust data, suppco_get_product_trust_score, so an agent can distinguish it without opening either 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?

Gives concrete triggering scenarios ("tell me about <product>", hydrating ids from the user's stack) and an explicit exclusion routing to suppco_get_product_trust_score for TrustScore rationale, certifications, and testing. The name-vs-id fallback is also clarified.

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

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