insourcia

get_events

Read-onlyIdempotent

Timeline unifiee des evenements d'UNE entreprise (par SIREN).

Fusionne cessions[] + procedures[] + dates scalaires (depot_comptes, augmentation_capital, marche_public, subvention, radiation, creation) en un flux chronologique decroissant.

Utiliser cet outil pour une entreprise a la fois. Pour de la prospection cross-SIREN, utiliser search_events.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Filtrer par type(s) d'evenement (CSV)
`limit`	No	Nombre d'evenements (defaut 50, max 200)
`siren`	Yes	SIREN a 9 chiffres
`offset`	No	Pagination (defaut 0)
`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."
`date_max`	No	Date max (YYYY-MM-DD)
`date_min`	No	Date min (YYYY-MM-DD)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`siren`	Yes
`pagination`	Yes
`denomination`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds valuable behavioral context beyond those hints: it discloses that the tool fuses cessions[], procedures[], and scalar dates into a single descending chronological stream. This gives the agent a clear model of the returned timeline's structure.

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 compact: three sentences, with the core purpose and merging behavior front-loaded and the sibling alternative in the final sentence. Every sentence contributes meaningful routing or behavioral information with no filler.

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 tool with a rich output schema, complete input schema, and safety annotations, the description covers the essential operational context: what events are merged, how they are ordered, the single-company constraint, and when to route to search_events. Nothing critical is missing for correct selection and invocation.

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?

The input schema has 100% description coverage for all parameters, so the schema already documents each parameter's meaning. The description reinforces the SIREN-based single-company scope and the timeline semantics, but does not add significant per-parameter detail beyond the schema.

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 states a specific verb and resource: it returns a unified, chronological event timeline for a single company (by SIREN), merging multiple event sources into one decreasing flow. It also explicitly distinguishes itself from the sibling search_events, making the tool's scope unmistakable.

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 says to use this tool for one company at a time and directs the agent to search_events for cross-SIREN prospecting. This clear 'when to use vs. alternative' guidance fully satisfies the dimension.

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?