Skip to main content
Glama
Quaestor-Technologies

Standard Metrics MCP Server

get_metrics_options

Retrieve available metric categories and options. Filter by category name, standard or custom type, and paginate results.

Instructions

Get available metric categories and options.

Args: category_name: Filter by specific category name is_standard: Filter by standard vs custom metrics page: Page number for pagination (default: 1) per_page: Results per page (default: 100, max: 100)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_nameNo
is_standardNo
pageNo
per_pageNo

Implementation Reference

  • MCP tool handler for get_metrics_options. Decorated with @mcp.tool, accepts optional parameters (category_name, is_standard, page, per_page) and delegates to client.get_metrics_options(). The decorator automatically registers it as an MCP tool named 'get_metrics_options'.
    @mcp.tool
    async def get_metrics_options(
        category_name: str | None = None,
        is_standard: bool | None = None,
        page: int = 1,
        per_page: int = 100,
    ) -> PaginatedMetricOptions:
        """Get available metric categories and options.
    
        Args:
            category_name: Filter by specific category name
            is_standard: Filter by standard vs custom metrics
            page: Page number for pagination (default: 1)
            per_page: Results per page (default: 100, max: 100)
        """
        async with StandardMetrics() as client:
            return await client.get_metrics_options(
                category_name=category_name,
                is_standard=is_standard,
                page=page,
                page_size=per_page,
            )
  • src/server.py:78-78 (registration)
    The wildcard import `from src.tools import *` registers all tools (including get_metrics_options) on the FastMCP server instance via the @mcp.tool decorator.
    from src.tools import *  # noqa: F403 - need to register all of the tools
  • Client method `get_metrics_options` on the StandardMetrics class. Makes a GET request to 'v1/metrics/options/' with optional query params (category_name, is_standard, page, page_size) and returns a PaginatedMetricOptions model.
    async def get_metrics_options(
        self,
        *,
        category_name: str | None = None,
        is_standard: bool | None = None,
        page: int = 1,
        page_size: int = 100,
    ) -> PaginatedMetricOptions:
        """Get available metric categories and options."""
        params: dict[str, Any] = {"page": page, "page_size": page_size}
        if category_name:
            params["category_name"] = category_name
        if is_standard is not None:
            params["is_standard"] = is_standard
        response = await self._request("GET", "v1/metrics/options/", params=params)
        return PaginatedMetricOptions.model_validate(response)
  • MetricOption Pydantic model schema defining the shape of each metric option returned (category_name, category_id, is_standard, type, is_point_in_time, is_archived, description, is_multiple, choices).
    class MetricOption(pydantic.BaseModel):
        category_name: str
        category_id: str
        is_standard: bool
        type: str
        is_point_in_time: bool
        is_archived: bool
        description: str = ""
        is_multiple: bool
        choices: list[str] | None = None
  • PaginatedMetricOptions type alias: PaginatedResponse[MetricOption] - the generic paginated wrapper for the list of MetricOption items.
    PaginatedMetricOptions = PaginatedResponse[MetricOption]
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention idempotency, rate limits, authentication, or any side effects. Basic read behavior is implied but not explicitly stated.

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 concise with a clear first line and a structured arg list. No extraneous sentences.

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?

The description covers the tool's purpose and all parameters, but lacks details on output format, pagination behavior beyond defaults, and any prerequisites. For a simple list tool, it is adequate but not thorough.

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?

With 0% schema description coverage, the description compensates by explaining each parameter's purpose: filtering by category, standard/custom, pagination. However, the explanations are minimal and do not add depth beyond the parameter names.

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 states 'Get available metric categories and options', clearly indicating the verb and resource. It differentiates from sibling tools like get_company_metrics which retrieve actual metric values, though the title is missing.

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 such as get_company_metrics or get_company_recent_metrics. The description only states what it does, not when it's appropriate.

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