Skip to main content
Glama

Capital Signal: ASX announcements

Call scorecard

call_scorecard
Read-onlyIdempotent

One author's record in the calls ledger: calls, scored, open, hits, hit rate, average and median signed excess vs benchmark. author: 'me' (default) or an author id; an id without a label covers all its labels. Under 10 scored calls the result says it is noise. Suited to 'how good are my/their calls' questions. 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": "call_scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorNo'me' (default) or an author id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is supplemental — and it delivers: the 10-scored-call noise caveat, the meaning of an id without a label, the default author value, and 'Free' (no cost to call). It omits error behavior or what happens with an unknown author id, so not a 5.

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?

Dense and front-loaded: the metric list comes first, then parameter meaning, then the noise caveat, then the use case and cost. Telegraphic phrasing ('average and median signed excess vs benchmark') is efficient but slightly compressed for fast scanning.

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, so the description carries the return-value burden — and it does so by naming the reported metrics. With one documented parameter and full annotation coverage, the definition is nearly complete; only error/edge-case behavior for bad author ids is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter at 100% schema coverage the baseline is 3, but the description adds real semantics the schema lacks: 'me' is the default, and an author id without a label aggregates across all that author's labels. That aggregation rule is genuine meaning 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 names a specific resource — one author's aggregate record in the calls ledger — and enumerates exactly what it reports (calls, scored, open, hits, hit rate, average/median signed excess vs benchmark). That enumeration distinguishes it from the raw `calls` sibling without needing to name it explicitly.

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 a clear use case: 'Suited to how good are my/their calls questions', which tells the agent when to reach for aggregated scoring rather than raw call records. It does not name an alternative or state exclusions, so it stops short of 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