Skip to main content
Glama

Compraventa360 — PYMEs en venta (Ecuador)

Ver detalle de un negocio

get_business
Read-onlyIdempotent

Devuelve la información pública de un negocio publicado en Compraventa360 dado su ID (UUID). Incluye descripción pública, el precio de venta solicitado (asking_price_usd) y datos de verificación cuando existen; nunca cifras confidenciales (ingresos, ganancia operativa/EBITDA, empleados requieren NDA). Excluye anuncios de demostración y no incluye datos de contacto privados.

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": {
      "business_id": "<business_id>"
    },
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYesUUID del negocio (columna id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / business_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so safety is covered; the description goes further and discloses data scope the annotations cannot express — asking_price_usd and verification data are returned, while revenue, EBITDA and employee counts require an NDA, private contact data is withheld, and demo listings are excluded. It does not address behavior for a missing or unpublished ID, 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?

Three dense clauses, front-loaded with what is returned before the exclusion list, and nothing is pure filler. The parenthetical NDA enumeration is slightly heavy but each item carries real filtering value for an agent deciding if this tool answers its question.

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?

There is no output schema, so return values must come from the description — and they do, field by field, including what is deliberately omitted. The only remaining gap is the not-found / unpublished-ID case for a tool whose sole input is an identifier.

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?

With 100% schema coverage on a single parameter, the schema already carries the UUID format and pattern. The description only restates the identity of the argument (business ID as UUID), adding no new meaning such as what happens with a stale or non-existent ID.

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 concrete verb and resource ("Devuelve la información pública de un negocio") keyed by UUID, and pins the scope: public listing data only, never confidential figures. An agent can tell this is a single-entity detail fetch, distinct from the sibling search_businesses catalog lookup.

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 phrase "dado su ID (UUID)" implies you need an identifier first, which hints that search_businesses is the discovery path, but the tool never says so explicitly and gives no when-not-to-use conditions. Usage is inferable rather than stated.

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