Skip to main content
Glama
Sign In

Finance Database

by io.github.JerBouma
OverviewDiscussionsAdmin

show_options

Read-onlyIdempotent
    Show the valid values of a Finance Database filter (e.g. every sector or
    country) for an asset class.

    Use this before filtering an asset class tool so the exact values are known.
    Filters narrow the options to what actually occurs, e.g. the industries of
    the 'Health Care' sector in Germany.

    Returns:
        str: Compact JSON with the values and their total count.

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": {
      "asset_class": "<asset_class>"
    },
    "name": "show_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum values to return (default 100, maximum 500); the total count is always given.
filtersNoOptional filters narrowing the options, e.g. {'country': 'Netherlands'} to list only the sectors present in the Netherlands. Values may be comma-separated.
selectionNoThe filter to list the values of, e.g. 'sector', 'country', 'industry' (equities) or 'category', 'family' (ETFs). Leave empty for an overview of every filter.
asset_classYesThe asset class: equities, etfs, indices, currencies or cryptos.
include_delistedNoInclude values only used by delisted entries (equities and ETFs).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and determinism are covered. The description does add that filters narrow results to values that actually occur (e.g. Health Care industries in Germany) and that the response is compact JSON with a total count, which is useful beyond annotations, but it stops short of describing pagination interaction between limit and count beyond what the schema already says.

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-loaded with the core action in the first sentence, then usage guidance, then a Returns block. Every sentence is relevant, with only mild redundancy between the filter example and the schema's own filter example.

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 read-only option-listing tool with a fully documented schema and no output schema, the description supplies purpose, workflow placement, filter behavior, and return format (compact JSON plus total count). Nothing an agent needs to call it correctly is missing.

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% and each parameter (limit, filters, selection, asset_class, include_delisted) is already documented in the schema. The description reinforces the role of filters with a worked example but adds no syntax, defaults, or edge-case semantics beyond the schema; baseline 3 applies.

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?

States a specific verb and resource: show the valid values of a Finance Database filter for a given asset class, with concrete examples (sector, country). It is clearly a metadata/option-lookup tool rather than a data-retrieval one, distinguishing it from the equities/etfs/indices siblings, though it never names those siblings 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?

Explicitly prescribes the workflow: 'Use this before filtering an asset class tool so the exact values are known.' That gives a clear when-to-use and an implied alternative (the asset-class tools themselves), but offers no explicit when-not-to-use or note about calling it with no selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Finance Database toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources