Skip to main content
Glama
Sign In
openmarkets

openmarkets

by danchev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fund_operations

Retrieve operations data for a fund by providing its ticker symbol.

Instructions

Retrieve operations data for a specific fund.

Args: ticker (str): The symbol of the fund.

Returns: FundOperations | None: Operations data or None if unavailable.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_fund_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The description does not mention any behavioral traits such as read-only, error handling, or prerequisites. With no annotations provided, the description carries the full burden of behavioral disclosure but fails to add beyond stating it returns 'FundOperations | None'.

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 description is very short and to the point, with the essential information front-loaded. However, it could be slightly more informative without sacrificing conciseness.

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

Completeness2/5

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

Given the tool has only one parameter and no annotations, the description is too minimal. It does not explain what 'operations data' comprises, especially when contrasted with many more specific sibling tools. The existence of an output schema does not excuse the lack of context in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

The only parameter 'ticker' has 0% schema description coverage. The description adds 'The symbol of the fund' which is minimal and obvious from the parameter name. It does not explain the format or any constraints, so it adds little value over the schema.

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 clearly states the verb 'retrieve' and resource 'operations data for a specific fund'. It is specific enough to indicate the tool's purpose, though 'operations data' is somewhat vague compared to more specific sibling tools like 'get_fund_asset_class_holdings' or 'get_fund_bond_holdings'.

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 is provided on when to use this tool versus the many sibling tools that also retrieve fund-related information, such as 'get_fund_info' or 'get_fund_overview'. The description lacks context about the tool's specific use case or limitations.

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