Skip to main content
Glama
Quaestor-Technologies

Standard Metrics MCP Server

list_funds

Retrieve a paginated list of all funds associated with the firm using configurable page and per_page parameters.

Instructions

List all funds associated with the firm.

Args: page: Page number for pagination (default: 1) per_page: Results per page (default: 100, max: 100)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo

Implementation Reference

  • The MCP tool handler for 'list_funds'. Decorated with @mcp.tool, it accepts page/per_page parameters and delegates to the StandardMetrics client's list_funds method.
    @mcp.tool
    async def list_funds(
        page: int = 1,
        per_page: int = 100,
    ) -> PaginatedFunds:
        """List all funds associated with the firm.
    
        Args:
            page: Page number for pagination (default: 1)
            per_page: Results per page (default: 100, max: 100)
        """
        async with StandardMetrics() as client:
            return await client.list_funds(page=page, page_size=per_page)
  • The StandardMetrics client method that makes the actual HTTP GET request to the 'v1/funds/' API endpoint and returns PaginatedFunds.
    async def list_funds(
        self,
        *,
        page: int = 1,
        page_size: int = 100,
    ) -> PaginatedFunds:
        """List all funds associated with the firm."""
        params: dict[str, Any] = {"page": page, "page_size": page_size}
        response = await self._request("GET", "v1/funds/", params=params)
        return PaginatedFunds.model_validate(response)
  • The Fund Pydantic model defining the schema for fund data (id, name, size, vintage, currency).
    class Fund(pydantic.BaseModel):
        id: str
        name: str
        size: str
        vintage: int
        currency: str
  • The PaginatedFunds type alias, which is a PaginatedResponse parameterized with the Fund model.
    PaginatedFunds = PaginatedResponse[Fund]
  • src/server.py:78-78 (registration)
    The wildcard import from src.tools in server.py triggers the @mcp.tool decorators, registering list_funds (and all other tools) with the MCP server.
    from src.tools import *  # noqa: F403 - need to register all of the tools
Behavior2/5

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

No annotations are present, and the description does not disclose any behavioral traits such as rate limits, result size implications, or authentication needs beyond the read operation nature.

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?

Extremely concise: one-line purpose followed by parameter descriptions, with no redundant information.

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 simple list tool with two optional parameters and no output schema, the description covers the core functionality and parameter details, though it could mention response format or sorting.

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

Parameters5/5

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

The description adds meaningful context to the schema's bare parameters: 'page' for pagination, 'per_page' with default and max values, which the schema lacks.

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 it lists all funds associated with the firm, distinguishing it from siblings that list other entities like companies or budgets.

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 implies usage via parameter defaults but lacks explicit guidance on when to use this tool versus alternatives or any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Quaestor-Technologies/smx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server