Skip to main content
Glama

Get ACM-68000 signal

get_signal
Read-onlyIdempotent

The ACM-68000 signal for a listed security in its home market: ACM-200 TRADING (on the register), ACM-404 NOT ON THE REGISTER, ACM-451 READ THE FILING (a regulatory filing in the last three days, named). A bare ticker naming more than one issuer returns no signal but its candidates (add the exchange); a home market that does not answer returns an error, never a signal. ACM-000, ACM-300 and ACM-500 are reserved (ACM-68000 v1.1) and never served. ACM-403 HALTED is advisory: the markets carry no halt flag yet, so the answer links the market's halts page. Each signal has its page: https://acm-200.ai/, https://acm-403.ai/, https://acm-404.ai/, https://acm-451.ai/.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description discloses failure behavior, ambiguous-ticker handling, reserved codes that are never served, and the advisory nature of ACM-403. It also links each signal to its corresponding page, giving unusually rich behavioral context for a read tool.

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 description is dense but front-loads the primary signal definition and keeps the edge cases and code meanings relevant. It is longer than typical because the ACM signal system has many codes, but each sentence contributes necessary behavioral detail.

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?

For a one-parameter read tool with no output schema, the description covers what is returned, what the codes mean, error and ambiguity behavior, reserved values, and advisory halts. Nothing material is missing for an agent to invoke it correctly.

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?

The schema already fully documents the single identifier parameter (ISIN, ticker with exchange, LEI, CMR key). The description adds useful resolution semantics by explaining that a bare ticker naming multiple issuers returns candidates and that the exchange should be added.

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 states a specific resource and scope: 'The ACM-68000 signal for a listed security in its home market,' and defines the signal codes it returns. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as resolve_issuer.

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 clear usage conditions, including that an ambiguous bare ticker returns no signal but candidate names, and that a non-answering home market returns an error. It does not name an alternative tool or explicitly say when another sibling should be used instead.

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.