Skip to main content
Glama

Capital Signal: ASX announcements

Board track record

board_track_record
Read-onlyIdempotent

Each current director (chair first) of one ASX company with their record at other ASX companies: board seats, completed tenures, median annualised share-price return vs CS200EW over completed tenures of a year or more (scoredTenures says how many; under 2 is an anecdote), outcomes (takeovers with premium, administrations, delistings), capital raised and dilution - and up to 10 of those tenures with docKeys. Suited to 'who runs this company and have they done it before' and board-quality questions. Caveats: survivorship, price-only returns. Free.

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": {
      "symbol": "<symbol>"
    },
    "name": "board_track_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesASX ticker, e.g. 'SVM'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the bar is lower. The description still adds real substance beyond them: survivorship bias, price-only returns, the scoredTenures reliability threshold, the 10-tenure cap on docKeys, and that the call is free. It does not cover empty/missing data behavior, which is the remaining gap.

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?

Content is front-loaded: the returned fields come first, then the use case, then caveats. It is dense and the first sentence is long with nested parentheticals, but no sentence is filler and the ordering is logical.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so field by field including the docKeys cap. Caveats and intended questions are also present, leaving nothing essential an agent needs before calling with one required ticker.

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 exists and the schema already documents it fully as an ASX ticker with an example. The description adds the context that the symbol selects a single company whose directors are then expanded, but no extra syntax or edge-case detail. Baseline 3 applies at 100% coverage with 1 param.

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 (current directors of one ASX company, chair first) and enumerates what comes back: board seats, completed tenures, median annualised return vs CS200EW, outcomes, capital raised, dilution, plus docKeys. That is far more specific than the name alone. It stops short of naming a sibling such as person_profile, so the boundary is implied rather than stated.

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?

It gives explicit use contexts: "who runs this company and have they done it before" and board-quality questions. It also supplies a threshold for trusting the return statistic (scoredTenures under 2 is an anecdote). No when-not-to-use or explicit alternative tool is offered, which keeps 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.

Resources