Skip to main content
Glama

list_fundamental_analyzers

Read-only

List the single-stock fundamental analyzers available in QuanterLab.

    Returns each analyzer's code, human-readable name, a one-line
    blurb, and the list of extra parameters it accepts (beyond
    `ticker`). The analyzers run on quanterlab.com, from the Supplementary
    Data menu at the top of the site; this catalog lists what is there.
    It analyses nothing itself: a question about one company (to look it
    up or analyse it, its fundamentals or its SEC filings) is answered in
    the chat by show_company.
    

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_fundamental_analyzers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: the analyzers themselves execute on quanterlab.com via the Supplementary Data menu, and this tool only mirrors that catalog — useful framing that explains why the call returns a static list. It stops short of any note on catalog size or freshness, which keeps it from a 5.

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 list of returned fields is front-loaded in the first paragraph and every sentence carries information. The sentence about the Supplementary Data menu location is mildly extraneous detail for an API consumer, and the uneven line wrapping makes it slightly harder to scan than it needs to be.

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?

With no output schema, the description correctly takes on the job of explaining the return shape (code, name, blurb, accepted extra parameters), and it adds the routing rule to `show_company`. For a zero-parameter catalog tool, nothing an agent needs in order 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema baseline is 4 and there is nothing for the description to compensate for. The mention of extra parameters 'beyond `ticker`' describes returned metadata rather than inputs, which is accurate but does not add input semantics.

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?

Opens with a specific verb and resource ('List the single-stock fundamental analyzers'), then spells out exactly what each entry contains (code, name, blurb, extra parameters beyond `ticker`). The final sentence explicitly contrasts it with `show_company`, so an agent can separate a catalog-listing tool from a single-company lookup 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?

States the negative case directly: 'It analyses nothing itself: a question about one company (to look it up or analyse it, its fundamentals or its SEC filings) is answered in the chat by show_company.' That names the alternative and the condition that selects it, covering both when to use this tool and when not to.

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