Skip to main content
Glama

Look up an instrument

acubic_lookup_instrument
Read-onlyIdempotent

Looks up a stock, ETF, crypto asset or currency pair by ticker, ISIN or name: its identity, whether it is in Acubic's tradable universe, whether eToro and Trading 212 list it, and any equivalent product Acubic substitutes (e.g. a UCITS ETF). Identity only: no price, return or rating. To filter many by metrics use acubic_screen_universe.

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": {
      "query": "<query>"
    },
    "name": "acubic_lookup_instrument"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches.
queryYesA ticker (AAPL, BTCUSD), an ISIN (US0378331005) or part of a name.
localeNoThe language of this conversation.
asset_classNoLimit to one asset class.
response_formatNoconcise

Output Schema

NameRequiredDescriptionDefault
errorNo
matchesNo
degradedNoTrue when profile data could not be read (profile fields are null).
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior by disclosing that results include cross-broker listing status and substitute products (e.g. a UCITS ETF), which an agent would not otherwise expect from a 'lookup'. It stops short of describing match/pagination behavior when several candidates match, which is the one remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler: the capability and its full return surface come first, then the negative scoping and the sibling pointer. The parenthetical UCITS example is the only flourish and it earns its place by making 'substitute' concrete.

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?

With an output schema present the description need not document return shapes, and it still covers the identity/exclusion boundary and sibling routing well. The minor omission is what to expect when several instruments match a name query beyond the default limit of five.

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 80%, so the schema already documents query formats, the locale enum, asset_class and the match limit. The description restates the identifier forms (ticker/ISIN/name) but adds no format examples or guidance on narrowing a query, so baseline 3 applies.

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?

States a specific verb (looks up) and resource (instrument) and enumerates the accepted identifier types (ticker, ISIN, name) plus the four asset classes covered. It also spells out exactly what identity attributes come back — tradable-universe membership, eToro/Trading 212 listing, and Acubic substitute products — which is far more than the title conveys.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly bounds the tool with 'Identity only: no price, return or rating' and names the correct alternative for the excluded case ('To filter many by metrics use acubic_screen_universe'). Both the when-not and the substitute sibling are stated outright, leaving nothing to inference.

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