Skip to main content
Glama

Share Repurchase Programs

GetBuybackPrograms
Read-only

Get a company's share-repurchase (buyback) picture: tracked programs (announcement date, authorized total in money or shares, remaining availability, expiry, source filings), the latest authorization figures, and repurchase history: cash spent, shares repurchased and average price per fiscal year and recent quarters. Figures come from the company's XBRL facts plus verified extractions of its filings' narrative text and its press releases, including a Canadian normal course issuer bid's maximum number of shares; nothing is estimated, and figures a company stopped restating carry a staleness label. For a B3 listing (BVMF:TICKER) it also lists every board-approved program, newest first: approval and end dates, status, the most shares it may buy of each kind and class against that class's free float, whether bought shares are cancelled or kept in treasury, and the company's treasury shares. For at-the-market (ATM) equity offering programs, the dilution mirror image, see GetAtmPrograms.

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": {
      "ticker": "<ticker>"
    },
    "name": "GetBuybackPrograms"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XTSE:WDO, BVMF:VALE3) for a listing outside the US.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XTSE:WDO) for a listing outside the US."New value: +"Stock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XTSE:WDO, BVMF:VALE3) for a listing outside the US."
  2. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol (e.g., AAPL, MSFT)."New value: +"Stock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XTSE:WDO) for a listing outside the US."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, so the description's job is to add context beyond safety, and it does: data provenance (XBRL facts plus verified extraction of filings' narrative text and press releases), a data-quality caveat ('nothing is estimated'), and a staleness label on figures a company stopped restating. It also discloses special-case coverage (Canadian NCIB maximum share count, B3 board-approved program details). This is exactly the kind of trust and interpretation context annotations cannot carry.

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, then progressively more specialized detail, ending with the sibling cross-reference. The sentences are very long and list-heavy (the B3 clause in particular), which costs a point, but no sentence is padding — each covers a distinct data domain or caveat.

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?

With no output schema, the description must carry the return-value burden, and it does: it enumerates fields (announcement date, authorized total, remaining availability, expiry, per-fiscal-year cash/shares/average price), notes the caveat markers, and covers regional variants. Nothing an agent needs to call this correctly 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% for the single ticker parameter, and the schema already documents both the plain-ticker and MIC:TICKER forms. The description repeats the BVMF:TICKER example but adds no syntax or validation detail beyond the schema, 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?

Opens with a specific verb+resource: 'Get a company's share-repurchase (buyback) picture', then enumerates exactly what is returned (tracked programs, latest authorization, repurchase history). It explicitly disambiguates from the sibling GetAtmPrograms as the 'dilution mirror image', so an agent can distinguish the two without opening a 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?

The final sentence gives an explicit routing rule to a named sibling: use GetAtmPrograms for at-the-market equity offering programs. The regional note ('For a B3 listing (BVMF:TICKER)') signals input-format-dependent behavior. It lacks an explicit 'do not use for X' for non-buyback capital-return questions, keeping it below a 5.

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.