Skip to main content
Glama

get_articles

Returns recent Siigo blog articles for a country, optionally filtered by topic. Each item has slug, title, excerpt, author, date, category, URL and the schema.org BlogPosting JSON-LD. Use this when the user wants up-to-date Siigo perspectives on accounting, taxes, PYMEs, fintech or product launches. Example calls: {"country": "COL", "limit": 10} for the latest across every category, or {"country": "COL", "topic": "derecho-laboral", "limit": 5} for one category.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional max number of articles to return. Default 10. Keep it at 25 or below: articles are fetched with the author embedded and WordPress silently returns an empty payload past ~25 items, so higher values yield zero articles.
topicNoOptional blog category slug. Must be one of the shell's six content categories: contabilidad-finanzas, gestion-administrativa, emprendimiento, derecho-laboral, obligaciones-fiscales, tecnologia-innovacion. Any other value returns an empty list. Omit to get the latest across all six.
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
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return payload shape (slug, title, excerpt, author, date, category, URL, JSON-LD), which is useful. However, it omits the ~25-item silent empty-payload limit and the unsupported-country behavior that the schema documents, and says nothing about auth or rate limits.

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-loaded with purpose, then return shape, then usage trigger, then examples — a sensible ordering with no filler sentences. The two inline JSON example calls are slightly verbose but each demonstrates a distinct invocation mode, so they largely earn their place.

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 no output schema, the description correctly compensates by listing every returned field and noting the embedded JSON-LD. Combined with a fully-specified input schema, an agent has enough to call it correctly; only pagination and failure modes are unaddressed, and those are largely handled in the parameter descriptions.

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 three parameters are already fully documented in the input schema, including the enum values and the 25-item cap rationale. The description only restates the optional topic filter and shows example combinations, adding little semantic meaning beyond the schema. 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 recent Siigo blog articles'), scopes it by country and optional topic, and enumerates the returned fields. This distinguishes it clearly from siblings like get_page_structured_data or search, which could otherwise seem overlapping.

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?

Explicitly says when to reach for it: 'Use this when the user wants up-to-date Siigo perspectives on accounting, taxes, PYMEs, fintech or product launches.' The two example calls show the filtered vs unfiltered invocation patterns. It does not name an alternative tool or state when NOT to use it, so it falls short of a 5.

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