Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

fr_accords_text

Read-only

Full text of a company agreement (accord d'entreprise) by its DILA id — fetched on demand from Légifrance (the local ACCO index only has metadata). Chain after fr_accords_search / fr_accords_get.

Returns metadata + texte (extracted from the filed docx; may be empty when no integral version was published) + texte_chars/offset/ next_offset + permalien (verifiable link, 404s honestly when the text is absent) + lien_construit (best-effort Légifrance pattern, not guaranteed to resolve).

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": {
      "acco_id": "<acco_id>"
    },
    "name": "fr_accords_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
offsetNostart position in the text. Long agreements come back in chunks: when `tronque` is true, call again with offset=`next_offset` to get the rest (health/pension clauses and final provisions usually sit at the END of a merger agreement).
_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.
acco_idYesDILA id (ACCOTEXT000…) from fr_accords_search results.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint=true, it discloses on-demand remote fetching from Légifrance, that `texte` may be empty when no integral version was published, that long texts are chunked via offset/next_offset, and that `permalien` 404s honestly while `lien_construit` is best-effort and may not resolve. These are exactly the failure modes an agent needs to plan around.

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?

Front-loaded with the core purpose in the first clause, then return-value notes. Slightly dense with parenthetical asides, but every sentence carries information about retrieval or result shape.

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?

No output schema exists, yet the description enumerates the returned fields (metadata, texte, texte_chars, offset, next_offset, permalien, lien_construit) and their caveats, so an agent knows what to expect and how to continue paging.

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 description coverage is 100%, so acco_id and offset are already documented in detail, including the next_offset continuation hint. The description restates the acco_id meaning and mentions offset/next_offset in its return summary but adds no new parameter meaning, so baseline 3 applies.

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 ('Full text of a company agreement ... by its DILA id') and explicitly distinguishes itself from the local ACCO index, which 'only has metadata'. An agent can immediately tell this retrieves content that the sibling search/get tools do not return.

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 says to 'Chain after fr_accords_search / fr_accords_get', giving clear sequencing and naming the prerequisite tools. It does not state when NOT to call it (e.g. when metadata alone suffices), which keeps it just short of a 5.

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