Skip to main content
Glama

Vigilar empresa

vigilar_empresa

Crea una vigilancia de una o varias EMPRESAS concretas (competidores, clientes, proveedores) y avisa por email cuando tengan movimientos en el dinero público: contratos, subvenciones o cambios mercantiles. Para vigilar un TEMA (un sector o tipo de ayuda) usa crear_alerta; esta es para empresas con nombre y apellidos. Toma 'empresas' (nombres o NIFs separados por comas; por cada nombre se busca su NIF). IMPORTANTE: llama primero con confirmar=false (por defecto) para mostrar al usuario qué empresas se van a vigilar y pedir su visto bueno; solo cuando lo confirme, vuelve con confirmar=true. Es una función de pago. Requiere iniciar sesión. Coste: 0; por cada nombre que haya que resolver a NIF, 5 créditos. Se mantienen los límites y confirmaciones del plan.

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": {
      "empresas": "<empresas>"
    },
    "name": "vigilar_empresa"
  }
}

Input Schema

NameRequiredDescriptionDefault
empresasYesEmpresa(s) a vigilar, separadas por comas: nombres (ej. 'Telefónica, Acme S.L.') o NIFs (ej. 'A82018474'). Por cada nombre se busca su NIF.
confirmarNoDéjalo en false (por defecto) para ver primero qué empresas se van a vigilar; vuelve a llamar con true para crear la vigilancia.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries real weight and delivers: it is a paid feature, requires a session, triggers outbound email on contracts/subsidies/registry changes, and applies plan limits and confirmations. The cost model is disclosed precisely (0 base, 5 credits per name resolved to a NIF), which is behavior no structured field conveys.

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 and well ordered: purpose, contrast with sibling, input format, confirmation protocol, then pricing. It loses a point because the confirmar=false/true flow is restated in the description, the schema, and again implicitly in the cost sentence, adding some redundancy for a two-parameter tool.

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?

Covers everything an agent needs for a mutation-ish watch-creation tool with no output schema: what gets created, what event fires the notification, auth and billing preconditions, the required user-approval loop, and cost. Nothing material is left to inference.

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 both parameters are already documented and the baseline is 3. The description still adds meaning by tying the comma-separated names-or-NIFs format to the cost driver (each name triggers a NIF lookup at 5 credits) and by reinforcing the confirmar two-phase protocol, which matters for correct invocation sequencing.

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 ("Crea una vigilancia de ... EMPRESAS concretas") plus the trigger and delivery channel (public-money movements, email notice). It explicitly contrasts with the sibling crear_alerta, which targets topics rather than named companies, so an agent can pick correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (specific companies: competitors, clients, suppliers), an explicit when-not-to-use with the named alternative (crear_alerta for sectors or aid types), and a mandatory two-step workflow: first confirmar=false to get user approval, then confirmar=true. Prerequisites (login, paid plan) are stated up front.

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.