Skip to main content
Glama

Capital Signal: ASX announcements

Company profile

company_profile
Read-onlyIdempotent

Profile of one ASX company: market cap and its date, sector, business description, operating projects with stage and commodities, latest cash position (with dataAsOf and possiblyStale), latest trading/guidance numbers, reported results for the latest full-year and half-year periods (revenue, profit, balance sheet, cash flow and per-share figures, each with its doc_key and page, in the reporting currency with an A$ conversion) a P/E on the latest close where it cross-checks, and EV/EBITDA (market cap + borrowings + lease liabilities - cash, over FY EBITDA) only where debt is known, otherwise withheld with the reason in evCheck (n/a for banks, insurers and other financials), board and executives, tags, and its eight most recent filings with doc_keys. Suited to a first look at a single named company or ticker ("What's going on with EMR?"). 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": "company_profile"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low, yet the description adds genuine behavioral context: staleness signalling via dataAsOf/possiblyStale, the condition under which EV/EBITDA is withheld with a reason in evCheck (n/a for banks, insurers and other financials), the A$ conversion alongside reporting currency, and that filings are capped at the eight most recent. What it omits is cost/latency beyond 'Free' and what happens when the symbol is unknown.

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 purpose is front-loaded in the first clause and the usage hint is placed at the end, which is a sound structure. However, the middle is a single ~110-word run-on of enumerated fields with nested parentheticals (the EV/EBITDA calculation and evCheck explanation in particular), which is dense to parse even though every clause carries real 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?

With no output schema, the description carries the full burden of describing the return payload, and it does so thoroughly — including derived-metric formulas, withholding conditions, currency handling, and provenance fields like doc_key and page. Given a one-parameter read tool with full annotation coverage, an agent has enough to decide to call it and to interpret the response.

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?

There is a single parameter and schema coverage is 100%, with the schema itself giving the format example "ASX ticker, e.g. 'BHM'". The description only adds the phrase 'single named company or ticker', which is useful in signalling scope but does not clarify whether a company name is actually accepted when the parameter is a ticker field — a small ambiguity rather than added semantics. 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 opens with a specific resource and scope: 'Profile of one ASX company', then enumerates the concrete contents (market cap, sector, projects, cash position, results, ratios, board, filings). That is far more than a restatement of the title and lets an agent separate it from siblings like company_events, company_prices or person_profile. It stops short of explicitly naming a contrasting sibling, so it is clear but not routing-complete.

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?

One usage sentence is given: 'Suited to a first look at a single named company or ticker', with an example query. That establishes the intended context but offers no when-not guidance, no alternatives (e.g. use filing_text for a specific document, company_prices for price history), and no prerequisites or failure behavior for an unknown symbol.

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