Skip to main content
Glama

get_compliance_info

Returns tax-and-regulatory compliance information for Siigo's country (Colombia DIAN: RADIAN, UGPP, documento soporte, electronic invoicing rules; Mexico SAT: CFDI 4.0, Carta Porte, DIOT, timbrado). Each item exposes title, summary, last updated date, source URL and the schema.org BlogPosting JSON-LD. Use this when the user asks about Siigo's compliance posture or specific regulations. Example calls: {"country": "COL"} or {"country": "MEX"} for the full list, or {"country": "MEX", "regulation": "CFDI"} to narrow it down.

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_compliance_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY.
regulationNoOptional single-word filter forwarded to WordPress full-text search. Letters, digits, hyphen and underscore only — no spaces, max 100 chars. Working examples — Colombia: RADIAN, UGPP, IVA, renta, exogena, nomina; Mexico: CFDI, SAT, DIOT, timbrado. Do NOT reuse the multi-word regulation id echoed in the response (e.g. RETENCION_FUENTE): it matches nothing. Omit to get the 50 latest compliance items.

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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does meaningful work: it lists the returned fields, reveals that a regulation filter is forwarded to WordPress full-text search, and states the default cap of "the 50 latest compliance items" when no filter is given. It does not state auth requirements, error behavior for unsupported countries, or confirm read-only semantics explicitly.

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?

Front-loads purpose, then return shape, then the usage trigger, then examples — a logical order with no filler sentences. It is dense but every clause carries information; a single very long parenthetical of regulation names is the only place it drags slightly.

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 read tool with no output schema, the description supplies what would otherwise be missing: the shape of each returned item and the default 50-item behavior. Remaining gaps are minor (unsupported-country error behavior, whether empty results are possible), so an agent can call it correctly as-is.

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 both parameters already document their patterns, examples, and constraints in detail. The description reinforces this with usage examples ({"country": "MEX", "regulation": "CFDI"}) but adds no syntax or semantic detail beyond what the schema already provides; 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 and resource ("Returns tax-and-regulatory compliance information") and immediately scopes it to named regimes (DIAN/RADIAN/UGPP for Colombia, SAT/CFDI 4.0/Carta Porte for Mexico). This makes it clearly distinct from siblings like get_articles, get_organization_info, and search, which do not deal with regulatory content.

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 trigger ("Use this when the user asks about Siigo's compliance posture or specific regulations") and three concrete example calls showing both broad and narrowed retrieval. It stops short of naming a competing sibling to prefer for adjacent questions (e.g. general articles), so the when-not guidance is only implicit.

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