Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

fr_bilan

Read-only

Fetch one INPI/BCE annual filing with full financial ratios.

Returns: CA, EBE, EBIT, résultat net, marge EBE, autonomie financière, taux d'endettement, liquidité, vétusté, BFR, rotation stocks, crédit clients/fournisseurs, couverture intérêts. Use fr_bilans first to discover available dates.

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": {
      "siren": "<siren>",
      "date_cloture": "<date_cloture>"
    },
    "name": "fr_bilan"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
sirenYesSIREN number (9 digits).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
date_clotureYesExercise closing date (YYYY-MM-DD, e.g. "2024-12-31").

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds meaningful content beyond that: an enumerated list of the financial ratios returned (marge EBE, autonomie financière, BFR, couverture intérêts, etc.), which is valuable since no output schema exists. It still omits behavior for missing filings, whether ratios are reported or computed, and consolidated vs. social scope.

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?

Front-loaded with the action and resource, followed by the return payload and a routing instruction. The long ratio enumeration is dense but every token is a distinct field name and, with no output schema, none of it is waste.

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

Completeness4/5

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

For a two-required-parameter read tool with no output schema, the definition covers both the discovery prerequisite and the returned payload, which is most of what an agent needs. The remaining gap is behavioral edge cases such as no filing existing for the given closing date.

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?

Schema coverage is 100%, so the schema already documents siren (9 digits) and date_cloture (YYYY-MM-DD). The description adds one real constraint: date_cloture must be one of the dates surfaced by fr_bilans. That is a useful but narrow addition, so the baseline of 3 holds.

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 ("Fetch one INPI/BCE annual filing") plus the scope qualifier "with full financial ratios." It also implicitly contrast with the sibling fr_bilans (plural = list), so an agent can distinguish retrieval of a single filing from discovery of available filings.

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?

Explicitly instructs the agent to call fr_bilans first to discover available dates, which is the key prerequisite for the required date_cloture argument. It does not describe failure conditions (no filing at that date) or when a different source should be used instead, so it stops short of full when/when-not guidance.

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

All Tulina 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