Skip to main content
Glama

Mastering Financial Markets

Browse MFM datasets

list_datasets
Read-onlyIdempotent

List public MFM catalog entries, optionally filtered by kind or verification level, with explicit pagination. Catalog availability does not certify completeness of every financial indicator.

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": "list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo"company", "page" or "dataset".
limitNoEntries per page, 1 to 50.
offsetNoNumber of entries to skip, for pagination (0 = first page).
versionNoCatalog version returned by the first page; when it no longer matches, the call fails with «Catalog changed» and the listing should restart.
verification_levelNoOnly companies of this MFM audit level (1, 2 or 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"\"company\", \"page\" or \"dataset\"."
    • addedInput schema / properties / limit / description
      Added value: +"Entries per page, 1 to 50."
    • addedInput schema / properties / offset / description
      Added value: +"Number of entries to skip, for pagination (0 = first page)."
    • addedInput schema / properties / verification_level / description
      Added value: +"Only companies of this MFM audit level (1, 2 or 3)."
    • addedInput schema / properties / version / description
      Added value: +"Catalog version returned by the first page; when it no longer matches, the call fails with «Catalog changed» and the listing should restart."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two useful behavioral notes beyond that – pagination is explicit and catalog inclusion is not a data-completeness claim – but says nothing about return shape or default page size, so it only modestly exceeds the annotation baseline.

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 short sentences, front-loaded with the core action and scope, with the caveat placed last where it does not obstruct scanning. No redundant restatement of the title or annotations.

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?

For a read-only, five-optional-parameter listing tool with rich annotations, the description covers scope, filters, pagination and a data-quality caveat. With no output schema, a brief note on what a catalog entry contains would have closed the remaining gap.

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 every parameter including the version/«Catalog changed» restart behavior is already documented in the schema. The description only restates the kind and verification_level filters, adding no syntax or semantics beyond the structured fields – the baseline 3 for full coverage.

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 gives a specific verb and resource ("List public MFM catalog entries") plus the supported refinements (kind, verification level, pagination). It is clear about scope (public catalog) but does not distinguish itself from siblings such as screen_companies or search, which an agent may plausibly confuse it with.

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

Usage Guidelines3/5

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

Usage is implied by "catalog entries" and the filter options, and the closing sentence warns that presence in the catalog is not a completeness guarantee. There is no explicit when-to-use versus an alternative tool, and no stated preconditions, so guidance remains inferential.

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