Skip to main content
Glama

Primary Source Commodities

Search Instruments

catalog.search
Read-onlyIdempotent

FREE. Resolve a human commodity name to an instrument code — 'cocoa' to CC, 'copper' to HG, 'palm oil' to PO. Use this instead of catalog.list when you already know the commodity by name and need the code to call price.latest or trade.flow. Returns nothing rather than a guess when no instrument matches. Free discovery tool — no payment required.

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": {
      "q": "<q>"
    },
    "name": "catalog.search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCommodity name, synonym, or instrument code, e.g. 'cocoa'
limitNoMaximum results (1-50, default 10)

Output Schema

NameRequiredDescriptionDefault
queryYesThe query as interpreted
resultsYesMatching instruments, most confident first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, and closed-world, so the safety profile is covered. The description adds two non-obvious behaviors not in the annotations: no-match returns nothing rather than a guess, and the call is free with no payment required. It stops short of describing ranking or ordering of multiple matches, but the essentials are disclosed.

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?

Front-loads cost ('FREE.') and the core action, then routes to the alternative, in three dense sentences. The trailing 'Free discovery tool — no payment required' restates the opening 'FREE,' so a small amount of the text does not earn its place.

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 two-parameter discovery lookup with a full output schema, the definition covers what it does, when to prefer it, its cost, and its no-match behavior — everything an agent needs to call it correctly. Return-value shape is legitimately left to the output schema.

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 description coverage is 100%, so both `q` and `limit` are already documented with the same 'name, synonym, or instrument code' phrasing the description uses. The example name-to-code pairs add illustrative value but no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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+resource pair — 'Resolve a human commodity name to an instrument code' — and backs it with concrete mappings ('cocoa' to CC, 'copper' to HG, 'palm oil' to PO). It explicitly distinguishes itself from catalog.list, so an agent can select it without opening either schema.

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?

Gives an explicit selection rule: 'Use this instead of catalog.list when you already know the commodity by name and need the code.' It also names the downstream tools that consume the result (price.latest, trade.flow), which tells the agent where this fits in a call chain.

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