insourcia

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

Apres l'ajout, communiquer l'URL a l'utilisateur pour qu'il retrouve sa liste dans l'app.

Input Schema

TableJSON Schema

Name	Required	Description
`siren`	Yes	SIREN a 9 chiffres de la societe a surveiller
`context`	Yes	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."
`list_name`	No	Nom de la liste cible (1-100 caracteres). Defaut: "Surveillance". La liste est creee automatiquement si elle n'existe pas.
`enable_alert`	No	true pour etre notifie des evenements futurs (BODACC, dirigeants...) sur les societes de la liste. Defaut: false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`siren`	Yes
`list_id`	Yes
`list_name`	Yes
`company_name`	Yes
`alert_enabled`	Yes
`already_watched`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (idempotentHint: true), the description adds concrete behavioral details: list auto-creation, idempotent already_watched=true behavior, daily alert semantics with future events only and no history replay, and the response fields. It also clarifies that the user should be given the resulting URL. This is rich and non-contradictory.

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 and usage guidance, followed by a compact 'Fonctionnement' bullet list covering the essential behaviors and the response shape. Every sentence carries operational value, including the closing instruction to communicate the URL to the user. It is thorough without being redundant.

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 fully equips an agent to invoke the tool correctly: clear selection criteria, parameter semantics, idempotency behavior, alert semantics, response format, and post-call instruction. With 100% schema coverage and an output schema present, nothing required for correct usage 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?

The schema already covers 100% of parameters, so the baseline is 3. The description adds extra meaning for list_name (default list 'Surveillance', auto-created) and enable_alert (daily frequency, future events only, no replay), going beyond the schema descriptions. Siren and context parameters gain nothing additional, but the overall semantic enrichment justifies a 4.

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 : l'ajoute a une liste de veille de l'utilisateur'. It clearly differentiates this tool from simple lookup by naming get_company as the alternative for mere 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: when the user wants to SUIVRE a company over time (acquisition target, competitor, client, risky supplier), and when not to use it: for simple consultation, with the explicit alternative 'utiliser get_company'. This gives an agent unambiguous selection criteria.

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

All insourcia tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Most tools have clearly distinct resource+action purposes, and the descriptions explicitly contrast near-neighbor tools like search_companies vs resolve_companies and get_events vs search_events. The only real risk is the trio of director-oriented tools, especially search_director_companies vs search_companies with dirigeant filters, which requires careful reading to avoid misselection.

Naming Consistency5/5

All 18 tools follow a consistent snake_case verb_noun pattern: search_, get_, list_, create_, watch_, unwatch_, mark_, resolve_. Singular names are used for single-entity actions and plural for list/search operations, making the pattern predictable. There is no camelCase, vague verb, or style mixing.

Tool Count4/5

18 tools is slightly above the ideal 10-15 range, but the count is justified by the broad domain covering search, company intelligence, watchlists, and news. Each tool appears to earn its place, and there are no obvious stubs or redundant duplicates. It feels a bit heavy but not bloated.

Completeness3/5

The company intelligence surface is very complete: search, deep company data, financials, directors, group graphs, events, and credit risk are all covered. Watchlists also have full add/remove/list coverage, but saved searches have a notable lifecycle gap—create and list exist, yet there is no update, delete, or alert-toggle for existing saved searches, creating a management dead end.

Resources

Need Help?