Skip to main content
Glama

Check product URL

check_product_url
Read-only

Check whether Pechincha.ai has an active deal for a product page URL from an online store. Returns the deal (price in BRL, discount, store, coupon, purchase link) and the lowest price across stores, or says there is none. Content in Brazilian Portuguese.

Input Schema

NameRequiredDescriptionDefault
urlYesProduct page URL at the store

Output Schema

NameRequiredDescriptionDefault
dealYesnull when Pechincha.ai has no active deal for the URL
product_idYes
product_urlYes
lowest_priceYesBRL, lowest price across stores
lowest_price_storeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / product_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "deal",
      -  "lowest_price",
      -  "lowest_price_store",
      -  "product_url"
      -]New value: +[
      +  "deal",
      +  "lowest_price",
      +  "lowest_price_store",
      +  "product_id",
      +  "product_url"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / deal / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "coupon_code": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "discount_percent": {
      -        "anyOf": [
      -          {
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "id": {
      -        "type": "string"
      -      },
      -      "old_price": {
      -        "description": "BRL, price before the discount",
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "price": {
      -        "description": "BRL",
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "published_at": {
      -        "description": "ISO 8601",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "purchase_url": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "store": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "title": {
      -        "type": "string"
      -      },
      -      "url": {
      -        "description": "Deal page on Pechincha.ai",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "id",
      -      "title",
      -      "price",
      -      "old_price",
      -      "discount_percent",
      -      "store",
      -      "coupon_code",
      -      "published_at",
      -      "url",
      -      "purchase_url"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "coupon_code": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "discount_percent": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "image_url": {
      +        "description": "Product photo",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "old_price": {
      +        "description": "BRL, price before the discount",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "price": {
      +        "description": "BRL",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "published_at": {
      +        "description": "ISO 8601",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "purchase_url": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "store": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Deal page on Pechincha.ai",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "title",
      +      "price",
      +      "old_price",
      +      "discount_percent",
      +      "store",
      +      "coupon_code",
      +      "published_at",
      +      "url",
      +      "image_url",
      +      "purchase_url"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description is free to add value elsewhere: it discloses the negative outcome ('or says there is none'), the currency/locale of the data, and the cross-store lowest-price comparison. It does not mention rate limits, auth, or pagination, but for a read-only lookup those are minor.

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?

Two sentences, front-loaded with the core action and outcome, and each remaining clause earns its place by naming the returned fields and the 'none' case. No filler or restatement of the title.

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?

With an output schema present, the description needn't enumerate return values, and it correctly limits itself to the outcome semantics and the Portuguese-language caveat. The only omission is any relationship to the sibling lookup tools, which would help an agent route between them.

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 there is only one parameter, so the schema already documents 'url' as a product page URL at the store. The description adds only the loose constraint that it is an online-store product page; it contributes no format, normalization, or accepted-domain guidance beyond the schema.

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 (check) plus resource (Pechinha.ai active deal for a product page URL) and enumerates the payload shape (price in BRL, discount, store, coupon, link, lowest price across stores). This is clearly distinct from siblings like get_deal, get_product, or search_deals, which operate on IDs or queries rather than an external store URL.

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 description implies the trigger condition (the agent has a product page URL from an online store) but never states when to prefer this over get_product or get_deal, nor what to do when the caller lacks a URL. Usage is inferable from the input shape rather than explicitly guided.

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