Skip to main content
Glama
OldTemple91

koreafilings-mcp

get_pricing

Check current per-endpoint pricing on koreafilings.com. Retrieve the x402 wallet address, network, USDC contract, and price in USDC for each paid endpoint to confirm payment details upfront, without any cost.

Instructions

Fetch the current per-endpoint pricing for koreafilings.com.

This is a free call; it returns the x402 wallet address, network, USDC contract, and the price in USDC for each paid endpoint. Useful to confirm the payer will be settling on the expected chain before spending anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_pricing'. Decorated with @mcp.tool(), it creates a temporary client with a dummy key (free endpoint), calls the SDK's get_pricing(), closes the client, and returns the Pricing model as a dict.
    @mcp.tool()
    def get_pricing() -> dict[str, Any]:
        """Fetch the current per-endpoint pricing for koreafilings.com.
    
        This is a free call; it returns the x402 wallet address, network,
        USDC contract, and the price in USDC for each paid endpoint. Useful
        to confirm the payer will be settling on the expected chain before
        spending anything.
        """
        network = os.environ.get("KOREAFILINGS_NETWORK", "base-sepolia").strip() or "base-sepolia"
        base_url = os.environ.get("KOREAFILINGS_BASE_URL", "https://api.koreafilings.com").strip()
        probe = Client(private_key="0x" + "00" * 32, network=network, base_url=base_url)
        try:
            pricing = probe.get_pricing()
        finally:
            probe.close()
        return pricing.model_dump(by_alias=True)
  • The Pricing Pydantic model returned by get_pricing(). Contains fields: x402_network, x402_asset, x402_recipient, and a list of PricingEndpoint objects.
    class Pricing(BaseModel):
        """Machine-readable pricing descriptor from ``GET /v1/pricing``."""
    
        model_config = ConfigDict(populate_by_name=True, frozen=True)
    
        x402_network: str = Field(alias="x402Network")
        x402_asset: str = Field(alias="x402Asset")
        x402_recipient: str = Field(alias="x402Recipient")
        endpoints: List["PricingEndpoint"]
  • The PricingEndpoint sub-model within Pricing, containing method, path, price_usdc, and description for each endpoint.
    class PricingEndpoint(BaseModel):
        model_config = ConfigDict(populate_by_name=True, frozen=True)
    
        method: str
        path: str
        price_usdc: str = Field(alias="priceUsdc")
        description: str
  • The SDK-level Client.get_pricing() method. Makes an HTTP GET to /v1/pricing and deserializes the response into the Pricing Pydantic model.
    def get_pricing(self) -> Pricing:
        """Fetch the public pricing descriptor. No payment required."""
        resp = self._http.get(f"{self._base_url}/v1/pricing")
        if resp.status_code != 200:
            raise ApiError(resp.status_code, _safe_json(resp))
        return Pricing.model_validate(resp.json())
  • Registration of the get_pricing tool via the @mcp.tool() decorator on line 77. FastMCP registers it automatically when the decorator is applied.
    @mcp.tool()
Behavior4/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. It discloses the call is free and returns specific fields (x402 wallet address, network, USDC contract, price in USDC). This gives good behavioral context, though it doesn't mention authentication or rate limits, which are likely unnecessary for a free, parameterless call.

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?

Three sentences with no wasted words. First sentence states purpose, second details output, third gives usage guidance. It is appropriately sized and front-loaded.

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

Completeness5/5

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

Given zero parameters and the existence of an output schema (though not shown), the description mentions what the call returns and explains when to use it. It covers the necessary context for a simple tool.

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

Parameters4/5

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

There are no parameters, and schema coverage is 100%, so baseline is 4. The description adds no extra parameter info because none exist, but that's appropriate.

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?

Description clearly states the tool fetches current per-endpoint pricing for koreafilings.com. The verb 'Fetch' and resource 'current per-endpoint pricing' are specific. Sibling tools are about filings and disclosures, so this tool is distinct.

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

Usage Guidelines4/5

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

Description explicitly notes it's a free call and useful for confirming the payer will settle on the expected chain before spending. This implies when to use it, though it doesn't provide explicit exclusions or alternatives. Nevertheless, the context is clear.

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/OldTemple91/korea-filings-api'

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