Skip to main content
Glama

get_products

Returns Siigo's catalog of products/plans for a country with price, currency and feature list, read from the pricing page (its schema.org Product graphs, or the shell catalogue where the country publishes one). Use this when the user asks about pricing, plans, discounts or what's included in each tier. price is the list price of the headline plan (yearly when there is one) and never includes a discount. offers holds every published price; an offer whose description ends in "con descuento" is a discount in force, with regularPrice (the list price it replaces) and discountPercent when the source publishes them. monthlyEquivalent is the per-month figure the pricing card shows for a multi-month plan (period total divided by its months), not the price of the monthly plan. Example call: {"country": "COL"} (uses the configured default slug precios-siigo). An empty products array means the page currently publishes no products.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "get_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional WP page slug whose JSON-LD exposes the Product/Offer graphs. Defaults to ContentProviders:{country}:ProductsSlug (COL: precios-siigo). Ignored for countries whose shell publishes a catalogue endpoint (ContentProviders:{country}:Webapp:ProductsListUrl): there the whole catalogue is returned. Same slug rules as get_page_structured_data. Example: precios-siigo.
countryYesISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU."New value: +"ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY."
    • changedInput schema / properties / country / examples
      Previous value: -[
      -  "COL",
      -  "MEX",
      -  "ECU"
      -]New value: +[
      +  "COL",
      +  "MEX",
      +  "ECU",
      +  "PER",
      +  "CHL",
      +  "URY"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/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 substantial work: it discloses the data source (parsed JSON-LD Product graphs vs. a shell catalogue endpoint), that the slug is ignored for shell countries, and that an empty products array means nothing is published. It does not mention auth needs, rate limits, or caching, so there is still a gap for a scraper-backed read tool.

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?

Purpose and the when-to-use trigger are front-loaded, then field semantics follow. The sentence defining price, offers and monthlyEquivalent earns its space because there is no output schema, though the slug-parsing detail duplicates what the schema already states.

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?

For a two-parameter tool with no output schema, the description is genuinely helpful: it defines the key return fields (price is list price excluding discounts, offers carries discount entries with regularPrice/discountPercent, monthlyEquivalent is a per-month equivalent, not the monthly plan), plus the empty-result meaning. Only ancillary operational details (auth, rate limits, response shape beyond those fields) are absent.

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%, so both parameters are already documented in the schema, including the slug fallback to ContentProviders:{country}:ProductsSlug. The description mostly restates that fallback and adds only the example call and default slug, so it clears the baseline but adds no new parameter meaning.

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 and resource — returns the catalog of products/plans with price, currency and feature list, sourced from the pricing page. It is clearly not an articles or compliance tool, and it references get_page_structured_data only for slug rules rather than distinguishing when to prefer that sibling over this one, which keeps it from a 5.

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?

Gives an explicit when-to-use trigger: pricing, plans, discounts, or tier contents questions. It does not name conditions where another tool (e.g. get_page_structured_data or search) should be used instead, so there are no exclusions or alternatives spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources