Skip to main content
Glama
Sign In

LegalOne Entreprises

by fr.legalone
OverviewDiscussionsAdmin

List a company's filed documents

list_company_documents
Read-onlyIdempotent

Use this when the user wants to know which deeds or annual-accounts filings a company has registered (title and dates), with a link to download them from the INPI. Do not use to read financial figures; the documents themselves are not returned.

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>"
    },
    "name": "list_company_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYesFrench company identifier: 9 digits (spaces allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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, so the safety baseline is covered. The description adds meaningful context beyond that: the documents themselves are not returned, only a listing with a download link, which prevents an agent from expecting document contents.

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?

Two sentences, zero filler, with the usage condition and exclusion front-loaded. Every clause carries information the agent needs.

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, but the description compensates by stating exactly what is returned (titles, dates, download link) and what is not (the documents themselves). For a single-parameter read tool this is complete.

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?

Only one parameter and schema coverage is 100%, so the schema already fully documents the siren identifier. The description implies the input is a company but adds no extra syntax or format guidance, so the 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?

Specific verb (list) and resource (company's filed documents: deeds, annual-accounts filings) with stated return content (title and dates, download link from INPI). An agent can distinguish it from sibling tools like get_company or the BODACC notice tools without opening any schema.

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?

Explicit when-to-use (user wants to know which filings a company has registered) and an explicit exclusion (do not use to read financial figures). It does not name the specific sibling that should be used for financial figures, which keeps it just below a 5.

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

All LegalOne Entreprises 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