Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

Search French BODACC announcements

company_fr_legal_announcements_search

Searches BODACC public announcements by family, date window and/or department. Use when: Searches BODACC public announcements by family, date window and/or department. You need to search BODACC announcements across companies by family, date window and/or department. You are building a broad legal-announcement discovery or monitoring query. Avoid when: You need the event timeline of one known company; use company/fr/events. You are polling one company from a saved date; use company/fr/events with the since parameter. Limitations: Results reflect BODACC records matching the supplied filters and the public source’s current coverage. Announcement records are factual source items and do not by themselves constitute legal-risk interpretation. Price: 0.010 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records returned by this call. (minimum 1; maximum 100; default 25).
sinceNoEarliest publication or event date to include, in YYYY-MM-DD format.
untilNoLatest publication or event date to include, in YYYY-MM-DD format.
departmentNoOptional French department code used to restrict results geographically.
family_codeNoOptional BODACC announcement family code used to restrict legal-announcement results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
criteriaYesStructured value returned for “criteria” as defined by this API contract.
truncatedYesWhether additional matching records existed beyond the returned result limit.
total_countYesTotal number of matching records reported by the source or endpoint.
announcementsYesStructured value returned for “announcements” as defined by this API contract.
returned_countYesNumber of records included in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/legal-announcements-search API."
    • addedInput schema / properties / department / description
      Added value: +"Optional French department code used to restrict results geographically."
    • addedInput schema / properties / family_code / description
      Added value: +"Optional BODACC announcement family code used to restrict legal-announcement results."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records returned by this call. (minimum 1; maximum 100; default 25)."
    • addedInput schema / properties / since / description
      Added value: +"Earliest publication or event date to include, in YYYY-MM-DD format."
    • addedInput schema / properties / until / description
      Added value: +"Latest publication or event date to include, in YYYY-MM-DD format."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/legal-announcements-search API."
    • addedOutput schema / properties / announcements / description
      Added value: +"Structured value returned for “announcements” as defined by this API contract."
    • addedOutput schema / properties / criteria / description
      Added value: +"Structured value returned for “criteria” as defined by this API contract."
    • addedOutput schema / properties / returned_count / description
      Added value: +"Number of records included in this response."
    • addedOutput schema / properties / total_count / description
      Added value: +"Total number of matching records reported by the source or endpoint."
    • addedOutput schema / properties / truncated / description
      Added value: +"Whether additional matching records existed beyond the returned result limit."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses paid-call behavior (x402 payment consumption, free payment-required challenge, possible new payment on repeat) and explicitly states source records are not modified, complementing the annotations. This is especially valuable because readOnlyHint/idempotentHint are false and could otherwise signal mutation.

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?

The labeled sections (Use when/Avoid when/Limitations/Price) make the description scannable and front-loaded. However, the first sentence is repeated nearly verbatim in the 'Use when' section, adding a redundant sentence without new information.

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?

For a search tool with an output schema, the description covers usage context, exclusions, limitations, pricing, and payment behavior, which is more than enough for correct invocation. Missing details like accepted family-code values are not required given the schema and source-coverage caveat.

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?

All five parameters are already fully described in the schema (100% coverage), so the description carries little parameter-level burden. It adds only a high-level grouping of filters (family, date window, department) and no syntax or constraints beyond the schema.

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?

The description opens with a specific verb ('Searches') and identifies the exact resource ('BODACC public announcements') plus the main filters ('family, date window and/or department'). It also names a sibling tool (company/fr/events) for different use cases, so an agent can distinguish it from nearby company tools.

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

Usage Guidelines5/5

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

It gives explicit 'Use when' and 'Avoid when' sections with concrete conditions, and it names the alternative tool (company/fr/events) for timeline polling from a saved date. This is clear routing guidance rather than leaving the agent to infer when to call it.

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

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