Skip to main content
Glama

insourcia

by io.insourcia
OverviewDiscussionsAdmin

watch_company

Idempotent

Mise sous surveillance d'une societe : l'ajoute a une liste de veille de l'utilisateur, visible dans l'app Insourcia (page /lists).

Utiliser cet outil quand l'utilisateur veut SUIVRE une societe dans le temps (cible d'acquisition, concurrent, client, fournisseur a risque) - pas pour une simple consultation (utiliser get_company).

Fonctionnement :

  • list_name designe la liste cible ; la liste "Surveillance" est utilisee par defaut et creee automatiquement si besoin (idem pour toute liste nommee qui n'existe pas encore).

  • Idempotent : si la societe est deja dans la liste, l'appel renvoie already_watched=true sans creer de doublon.

  • enable_alert=true active une alerte quotidienne sur la liste : l'utilisateur est notifie des evenements FUTURS touchant les societes de la liste (annonces BODACC : procedures collectives, cessions... et changements de dirigeants). Pas de replay de l'historique.

Reponse : { siren, company_name (null si non renseignee), list_id, list_name, url (page /lists), already_watched, alert_enabled }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sirenYesSIREN a 9 chiffres de la societe a surveiller
list_nameNoNom de la liste cible (1-100 caracteres). Defaut: "Surveillance". La liste est creee automatiquement si elle n'existe pas.
enable_alertNotrue pour etre notifie des evenements futurs (BODACC, dirigeants...) sur les societes de la liste. Defaut: false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
sirenYes
list_idYes
list_nameYes
company_nameYes
alert_enabledYes
already_watchedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "siren",
-  "context"
-]New value: +[
+  "siren"
+]
  2. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "siren"
-]New value: +[
+  "siren",
+  "context"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining exactly what happens: auto-creation of lists, idempotent behavior with already_watched=true, daily alert semantics, future-only events with no history replay, and the response shape. It also aligns with idempotentHint=true and provides practical consequences of enabling alerts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose, then gives clear usage guidance, a labeled 'Fonctionnement' section, and a concise response outline. It is detailed but every sentence contributes meaningful behavioral or selection information, and the structure makes it easy to scan.

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?

The description covers the main use case, alternatives, parameter behavior, alert semantics, idempotency, response fields, and the Insourcia UI context. Given the tool's moderate complexity and the presence of a complete output schema, nothing essential is missing for an agent to call it correctly.

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 beyond the schema by explaining list_name as the target list, clarifying that any named list is auto-created, and detailing that enable_alert triggers a daily digest of future BODACC and director-change events. This is more than the schema alone provides, though not substantially more on the siren parameter.

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 opens with a specific verb and resource: 'Mise sous surveillance d'une societe' and 'l'ajoute a une liste de veille'. It clearly distinguishes the tool from get_company by stating this is for following a company over time, not simple consultation.

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?

The description explicitly states when to use the tool: 'Utiliser cet outil quand l'utilisateur veut SUIVRE une societe dans le temps', and names the alternative for the excluded case: 'pas pour une simple consultation (utiliser get_company)'. This leaves no ambiguity about tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All insourcia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources