Skip to main content
Glama
fauguste

boondmanager-mcp-server

Reporting sociétés

boond_reporting_companies
Read-onlyIdempotent

Generate company reports on revenue, margin, and activity for a specified date range. Filter by managers, agencies, periods, company states, and more.

Instructions

Reporting des sociétés (CA, marge, activité...). ⚠️ startDate + endDate (YYYY-MM-DD) sont REQUIS par l'API.

Filtres clés : périmètre (perimeterDynamic/perimeterManagers/perimeterAgencies...), période (period, periodDynamic), companiesStates, companies, maxCompanies, showPercentage. Les états/types sont des IDs entiers issus de boond_application_dictionary. Sans filtre de périmètre, le reporting porte sur tout le périmètre autorisé.

Returns: Données de reporting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNuméro de page (défaut: 1, max: 100)
endDateYesDate de fin (YYYY-MM-DD). Requis par l'API.
keywordsNoMots-clés.
pageSizeNoNombre de résultats par page (max: 500, défaut: 30)
useCacheNoCache de reporting : 'withCache' (valeurs mises en cache) ou 'withoutCache' (recalcul, défaut).
companiesNoFiltrer sur ces IDs de sociétés.
startDateYesDate de début (YYYY-MM-DD). Requis par l'API.
scorecardsNoIDs des scorecards (indicateurs) à retourner.
maxCompaniesNoNombre de sociétés par page (1-10, défaut 1). Le nombre de résultats = sociétés × indicateurs.
periodDynamicNoPériode dynamique relative à aujourd'hui (avec period='dynamicPeriod') : today, thisWeek, thisMonth, thisTrimester, thisSemester, thisYear, thisFiscalYear, yesterday, lastWeek, lastMonth, lastTrimester, lastSemester, lastYear, lastFiscalYear, tomorrow, nextWeek, nextMonth, nextTrimester, nextSemester, nextYear, nextFiscalYear, lastCustomPeriod, nextCustomPeriod.
perimeterPolesNoIDs de pôles. Conserve les entités dont le responsable appartient à ces pôles.
showPercentageNoAfficher les valeurs en pourcentage plutôt qu'en valeur réelle.
companiesStatesNoIDs d'états de sociétés (dictionnaire setting.state.company).
narrowPerimeterNoSi true, jointure ET entre les filtres `perimeter*` (au lieu de OU par défaut).
perimeterDynamicNoPérimètre dynamique relatif à l'utilisateur courant (raccourci sans avoir à connaître son propre ID). Valeurs : 'data' (mes propres données), 'managers' (mon équipe / mes N-1), 'agencies' (mes agences), 'poles' (mes pôles), 'businessUnits' (mes BU). Combinable.
perimeterAgenciesNoIDs d'agences. Conserve les entités dont le responsable appartient à ces agences.
perimeterManagersNoIDs des managers (ressources). Conserve les entités dont le responsable est l'un de ces managers. Pour 'mon équipe / N-1 d'une personne X', passer [X_id]. Obtenir son propre ID via boond_application_current_user.
perimeterBusinessUnitsNoIDs de business units. Conserve les entités dont le responsable appartient à ces BU.
periodDynamicParametersNoParamètres de la période personnalisée (utilisé avec periodDynamic=lastCustomPeriod/nextCustomPeriod).
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds context about required date parameters and perimeter behavior, which aligns with safe operation. No contradiction.

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?

The description is concise, starts with the purpose, then highlights required fields, and lists key filters. It uses a bullet-like structure with emojis for readability. No unnecessary sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 19 parameters and no output schema, the description does not detail the return format beyond 'Returns: Données de reporting.', which is vague. While annotations cover safety, the description could better specify what the reporting data contains (e.g., fields, structure). This gap lowers the score.

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% with detailed descriptions for all 19 parameters. The description adds a helpful summary of key filter categories, which aids in understanding without duplicating schema details. This is above the baseline of 3 for high coverage.

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 title and description clearly state this tool is for reporting on companies (revenue, margin, activity). It distinguishes itself from sibling tools like boond_companies_search (which searches companies) and other reporting tools by specifying the reporting domain. The description lists key filters and the purpose is unambiguous.

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

Usage Guidelines4/5

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

The description explicitly notes that startDate and endDate are required by the API, and explains that without perimeter filters the report covers the whole authorized perimeter. It references the dictionary for state/type IDs, providing context. However, it does not explicitly state when to use this tool versus alternatives like boond_reporting_projects or boond_reporting_resources, though the name implies the scope.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fauguste/boondmanager-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server