Hedge Fund Alpha Research

Search the HFA membership catalog

search_catalog

Read-onlyIdempotent

Search verified Hedge Fund Alpha membership products and prices using the UCP catalog search capability. Read-only; cannot create a checkout or charge a payment method.

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": {
      "meta": "<meta>",
      "catalog": "<catalog>"
    },
    "name": "search_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`meta`	Yes
`catalog`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 24, 2026

TDQS

B3.3/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 idempotentHint:true. The description reinforces these by stating it is read-only and cannot charge, and adds that the search is over 'verified' content. This adds value beyond annotations, though it could include additional behavioral details (e.g., pagination behavior, result format).

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 exceptionally concise at two sentences, with the core purpose in the first sentence and safety warnings in the second. No superfluous information is present, and key points are front-loaded.

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 complexity (nested objects, 2 required params, 0% schema coverage, no output schema), the description is far from complete. It omits parameter semantics, input format, and output expectations. An agent would need to infer too much to use this tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation of the 'meta' and 'catalog' parameters, which are complex nested objects. An AI agent would not understand how to structure the input, making this a critical gap. The description entirely fails to compensate for the lack of schema descriptions.

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 tool searches the HFA membership catalog for products and prices, with a specific domain and constraints. It uses 'search' as a strong verb and distinguishes the resource. However, it does not explicitly differentiate from sibling tools like search_hfa_content, which could cause ambiguity for an AI agent.

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?

The description mentions the tool is read-only and cannot create checkouts, providing some usage context. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., search_hfa_content, lookup_catalog), and does not mention prerequisites or failure scenarios.

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

All Hedge Fund Alpha Research tools Inspect

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

Need Help?