Skip to main content
Glama

BODACC Creditor Opposition Deadline Sentinel (France)

French creditor objection deadline: free sample

oppositions_example
Read-onlyIdempotent

Free sample: real output computed while an objection window was open. Same shape as oppositions_lookup.

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": "oppositions_example"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceNo
licenceNoLicence of the source data: nom, url, source, attribution (the credit the licence requires)
resultatsNo
date_calculNo
avertissementNo
entreprises_avec_delai_ouvertNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds genuinely useful context beyond them: the payload is real data captured during an open objection window, meaning it is a frozen snapshot rather than current results, and it mirrors another tool's schema.

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 short sentences with no filler, and the most important information ('free sample', snapshot nature) is front-loaded. Every clause carries meaning.

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?

With an output schema present and no parameters, the description needn't explain return values, and it correctly points at the sibling for shape. The remaining gap is a lack of explicit routing guidance about when to prefer oppositions_lookup over this sample.

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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description does not need to explain any argument semantics.

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

Purpose3/5

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

The description frames the tool as a 'free sample' whose output was 'computed while an objection window was open' and notes it matches 'oppositions_lookup' in shape, which does differentiate it from the sibling. However, it never states a verb+resource directly (e.g. 'returns a static example response'), so an agent must infer that this is a demo/preview rather than a live lookup.

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?

The 'free sample' framing plus 'same shape as oppositions_lookup' implies the intended use: previewing the response format instead of doing a real lookup. There is no explicit when-to-use/when-not statement or a direct instruction such as 'call oppositions_lookup for actual data'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.