rendita

Upcoming French ex-dates and payment dates

list_french_dividend_dates

Read-onlyIdempotent

The ex-dates and payment dates published by the companies listed in Paris in a window of days starting at a date (today by default, 30 days by default, 120 at most), with the amount per share and its status. Optionally the CAC 40 only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_french_dividend_dates"
  }
}

Input Schema

Name	Required	Description
`days`	No	Length of the window. 30 when left out.
`from`	No	First day of the window, YYYY-MM-DD. Today when left out.
`index`	No	Restrict to the CAC 40.

Output Schema

Name	Required	Description	Default
`date`	Yes
`fait`	Yes
`source`	Yes
`empreinte`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds the data provenance ('published by the companies listed in Paris') but says nothing about rate limits, freshness/lag of the published data, or empty-window behavior.

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?

A single dense sentence carries purpose, window defaults, returned fields, and the optional filter, with the scope stated up front. It reads somewhat run-on, and the '(today by default, 30 days by default, 120 at most)' clause duplicates the schema, but there is no padding.

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?

An output schema exists and the description still names the meaningful return fields (amount per share and its status), so return-value explanation is not needed. For a zero-required-parameter read tool with full schema coverage and annotations, nothing essential for correct invocation is missing.

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 the schema already documents all three parameters, including the 30-day default and the 120 maximum. The description merely restates those same defaults in prose without adding format, edge-case, or interaction guidance (e.g. what from+days combine to), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (French ex-dates and payment dates published by Paris-listed companies) and states the payload includes amount per share and status. It implicitly distinguishes itself from the sibling get_french_dividend by being a windowed list rather than a single lookup, though it never names the sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the window defaults (today, 30 days, 120 max) tell the agent the common case, but there is no statement of when to prefer this list view over get_french_dividend, and no exclusions or prerequisites are given.

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

All rendita tools Inspect

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

Need Help?