Skip to main content
Glama

get_organization_info

Returns canonical Organization data for Siigo in a country: legal name, URL, logo, social profiles (sameAs), address, phone and founding date — plus the full schema.org JSON-LD graphs for the 'about / por qué' page. Use this when the agent needs trustworthy company facts to cite Siigo as a source. Example call: {"country": "COL"}. The data is read from the country's home page (ContentProviders:{country}:Webapp:OrganizationSlug, COL: inicio), the only page that publishes the Organization graph; LocalBusiness and Corporation count as well.

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_organization_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.

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.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses provenance (read from the country's home page), the internal content path (ContentProviders:{country}:Webapp:OrganizationSlug), and that LocalBusiness and Corporation graphs also qualify as valid results. It stops short of describing failure behavior for unserved countries, caching/freshness, or response shape, which keeps it below a 5.

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?

It is front-loaded: the returned data is stated first, then the usage trigger, then the example, then provenance. Most sentences earn their place, though the internal key path 'ContentProviders:{country}:Webapp:OrganizationSlug, COL: inicio' is fairly jargon-heavy and could distract an agent that only needs the ISO code.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only lookup with no output schema, the description supplies what an agent needs: the concrete fields returned, the presence of full JSON-LD graphs, the data source, and a sample invocation. Nothing essential to calling it correctly or interpreting the result category is missing.

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 already 100% (pattern, ISO alpha-3 meaning, examples, and the DependencyInjection:ProfileInjector:Actives restriction), so the baseline is 3. The description adds value beyond the schema with a concrete example call ({"country": "COL"}) and the explanation that the parameter selects which country's home page is scraped, making the parameter's effect on the underlying source explicit.

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?

The description uses a specific verb and resource ('Returns canonical Organization data for Siigo in a country') and enumerates the exact fields returned (legal name, URL, logo, sameAs, address, phone, founding date, JSON-LD graphs). It also implicitly separates itself from siblings like get_page_structured_data by stating the home page is 'the only page that publishes the Organization graph', so an agent can tell what it gets here versus a generic structured-data call.

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?

It gives a clear usage trigger: 'Use this when the agent needs trustworthy company facts to cite Siigo as a source.' That is a genuine when-to-use condition. It does not, however, name an alternative tool or state when not to use this (e.g. for non-Organization data, use get_page_structured_data or get_compliance_info), so routing is clear but not fully comparative.

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