Skip to main content
Glama

search

Full-text search against Siigo's curated content for a country. Returns matching pages, posts, and resources. Use this when the user mentions a topic you don't have a more specific tool for. Example call: {"country": "COL", "query": "facturacion electronica"}. Note: the COL shell has search disabled until its cached search service ships, so it currently returns an empty items array — prefer get_articles or get_compliance_info meanwhile.

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>",
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text query against Siigo's WordPress content. Between 2 and 200 chars, no angle brackets. Examples: facturacion electronica, nomina, plan emprendedor.
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

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a critical behavioral quirk: COL currently returns an empty items array until its cached search service ships. It also states the return shape (pages, posts, resources), though it says nothing about result limits, ranking, or pagination.

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 usage rule, then the example, then the caveat. The inline example call largely duplicates the schema's own examples array, which is the one mildly wasteful element in an otherwise tight three-sentence definition.

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 search with no output schema, the description covers purpose, return shape, selection rule, and a known degraded-environment caveat. Remaining gaps (result caps, empty-result handling outside COL) are minor rather than blocking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds value by scoping the country parameter behaviorally (the COL shell is disabled) and by showing a concrete paired call that clarifies how country and query combine. It does not add syntax beyond what the schema's pattern/length constraints already state.

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 ('Full-text search against Siigo's curated content for a country') and names the returned entity types (pages, posts, resources). An agent can tell this apart from the sibling getters, which return single structured records rather than search hits.

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 a clear selection rule: 'Use this when the user mentions a topic you don't have a more specific tool for,' which routes topical queries here and specific ones to get_articles/get_compliance_info. The explicit alternative routing, however, is scoped only to COL, leaving other countries without named fallbacks.

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