Skip to main content
Glama
Sign In
openmarkets

openmarkets

by danchev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_sector_top_mutual_funds

Retrieve a list of top mutual funds within a specific sector to identify leading investment options.

Instructions

Retrieve a list of top mutual funds within a specific sector.

Args: sector (str): The name of the sector. Returns: list[SectorTopMutualFundsEntry]: A list of top mutual funds in the sector.

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": {
      "sector": "<sector>"
    },
    "name": "get_sector_top_mutual_funds"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so the description carries the full burden. It does not disclose behavioral traits like read-only nature, valid sectors, error handling, or rate limits. The description is minimal.

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?

The description is extremely concise and well-structured, with a clear action statement followed by Args and Returns sections. Every sentence is necessary and no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and an output schema, the description is adequate but lacking behavioral context and guidance. It does not explain what qualifies as 'top' mutual funds or how sectors are defined, which could be helpful given the sibling tools.

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?

The description adds a brief explanation for the parameter 'sector: The name of the sector,' which provides some meaning beyond the empty schema description. However, it lacks specificity such as examples or valid values. Given 0% schema coverage, more detail would be expected.

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?

The description clearly states what the tool does: 'Retrieve a list of top mutual funds within a specific sector.' It uses a specific verb and resource, and distinguishes from siblings like get_sector_top_companies and get_sector_top_etfs by focusing on mutual funds.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. With many sibling tools for sector data, there is no mention of context, prerequisites, or exclusions.

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

Deploy Server

Other Tools