Skip to main content
Glama

Capital Signal: ASX announcements

Calls

calls
Read-onlyIdempotent

Lists locked calls from the Capital Signal calls ledger: each with tickers, direction, horizon, thesis, evidence doc_keys, base rate, sha256 and canonical JSON (sha256 of canonical = the hash; verify against /calls.txt), and, once its horizon has passed, its score (return, benchmark return, signed excess, hit). status: open | scored | all; author: 'me' for the caller's own calls or an author id from a previous result; since: YYYY-MM-DD. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax calls (default 25, max 200; pages are kept under 30,000 characters).
sinceNoCalls locked on or after YYYY-MM-DD.
authorNo'me', or an author id such as 'u_1a2b3c4d5e' or 'u_1a2b3c4d5e/newsletter'.
cursorNoNext page: the nextCursor from the previous response. A non-null nextCursor means more calls follow; null is the last page.
statusNoDefault all.

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 readOnlyHint, idempotentHint and a closed-world non-destructive profile, yet the description adds real value: hash-verification against /calls.txt, and the rule that a score exists only once the horizon has passed. It still omits result ordering, lock semantics, and the paging cap, which the schema covers instead.

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?

One dense sentence front-loads the resource and its payload, then ends with compact filter semantics. The hash-verification and scoring clauses are packed into nested parentheticals that make it harder to scan.

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?

No output schema exists, but the description compensates by enumerating the returned fields and the score components (return, benchmark return, signed excess, hit), and paging is handled by the cursor parameter. What's missing is result ordering and what 'locked' means for the ledger.

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 coverage is 100%, so the parameters are documented adequately, and the description merely restates status, author ('me' or an author id from a previous result) and since (YYYY-MM-DD). It adds no syntax or behavior beyond the schema, which is the baseline-3 case.

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 definition gives a specific verb and resource ('Lists locked calls from the Capital Signal calls ledger') and enumerates the returned fields: tickers, direction, horizon, thesis, evidence doc_keys, base rate, sha256, canonical JSON, and score. It does not differentiate the tool from siblings like call_scorecard or board_track_record, so it stops short of a 5.

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?

Usage is implied through the filter parameters (status open|scored|all, author 'me' vs. an id from a previous result, since date), which tells an agent how to narrow results. However, it never states when to use this tool instead of call_scorecard or board_track_record, and it offers no exclusions or prerequisites.

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