Skip to main content
Glama

geographical_indication_pdo_pgi_audit

Read-onlyIdempotent

[EU geographical indications (PDO / PGI / TSG) single regulation audit. Statutory compliance check, read-only, side-effect free]. Audits protected designations under Regulation (EU) 2024/1143, evaluating raw material zoning restrictions, transformation criteria, control body accreditation, and Article 26 evocation risks. Usage: Pass product indication details and geographical provenance to audit legal validity of PDO, PGI, or TSG claims. Returns: JSON object with { productName: string, indicationType: string, registeredDenominationName: string, isPdoCriterionSatisfied: boolean, isPgiCriterionSatisfied: boolean, isTsgCriterionSatisfied: boolean, evocationOrMisleadingRiskDetected: boolean, statutoryAuditVerdict: string, complianceFindings: array }.

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": {
      "productName": "<productName>",
      "indicationType": "<indicationType>",
      "registeredDenominationName": "<registeredDenominationName>",
      "countryOfOriginIso2": "<countryOfOriginIso2>",
      "rawMaterialsOriginRestrictedToZone": "<rawMaterialsOriginRestrictedToZone>",
      "processingAllInDesignatedZone": "<processingAllInDesignatedZone>",
      "inspectionBodyCertificationCode": "<inspectionBodyCertificationCode>",
      "productSpecificationComplianceCertified": "<productSpecificationComplianceCertified>",
      "packagingMentionsOtherGeographicalHints": "<packagingMentionsOtherGeographicalHints>",
      "claimsTraditionalSpecialityRecipe": "<claimsTraditionalSpecialityRecipe>"
    },
    "name": "geographical_indication_pdo_pgi_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNameYesFinished commercial food/wine product name
indicationTypeYesType of geographical indication protection claimed
countryOfOriginIso2Yes2-letter ISO country code of Member State holding the registration
registeredDenominationNameYesOfficial protected denomination registered in eAmbrosia (e.g. Parmigiano Reggiano, Champagne, Prosciutto di Parma)
processingAllInDesignatedZoneYesWhether all stages of transformation take place in the delimited zone (mandatory for PDO, at least 1 stage for PGI)
inspectionBodyCertificationCodeYesAccredited control authority code assigned by Member State (e.g. IT-BIO-006, CSQA)
claimsTraditionalSpecialityRecipeYesWhether product follows traditional practice of at least 30 years (mandatory for TSG)
rawMaterialsOriginRestrictedToZoneYesWhether 100% of raw materials originate strictly within delimited geographical zone (mandatory for PDO)
packagingMentionsOtherGeographicalHintsYesWhether packaging references flags, places, or terms other than the registered denomination (Art. 26 evocation check)
productSpecificationComplianceCertifiedYesWhether product complies with registered disciplinary specification (Disciplinare di Produzione)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'read-only, side-effect free' while adding substantive context: the statutory basis (Reg. 2024/1143) and the specific criteria evaluated. It also discloses the return shape, which annotations cannot cover. It stops short of noting limits such as jurisdiction scope or what happens with unregistered denominations.

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?

Front-loaded with a bracketed scope statement, then a compact evaluation list, then explicit Usage and Returns sections. Every sentence carries information and the structure maps directly onto how an agent would plan the call.

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 ten required parameters and no output schema, the description compensates by enumerating the returned JSON fields, so the agent knows what a verdict looks like. The main residual gap is that the conditional requirements per indicationType (PDO vs PGI vs TSG) are left to the schema rather than summarized.

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%, so all ten parameters are already documented in the schema, including the PDO/PGI/TSG conditional logic. The description adds only the Article 26 framing for the evocation parameter and no format or validation detail beyond the schema, so 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 (audits) and resource (protected designations under Regulation (EU) 2024/1143), and enumerates the four evaluation axes: raw material zoning, transformation criteria, control body accreditation, and Article 26 evocation risk. This is clearly distinguishable from the sibling audits, which cover unrelated regulatory domains.

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 'Usage' line tells the agent to pass product indication details and geographical provenance to audit legal validity of PDO/PGI/TSG claims, which implies the triggering context. However, it offers no when-not guidance, no prerequisites (e.g. registration must exist in eAmbrosia), and no routing to alternatives.

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