Skip to main content
Glama
Fewsats

Sherlock Domains MCP

by Fewsats

get_purchase_offers

Retrieve payment options for domain purchases, including L402 offer details like cost, currency, and package information for processing.

Instructions

Request available payment options for a domain.
This method returns an L402 offer, which includes details such as offer_id, amount, currency, and more.
The returned offer can be processed by any tool supporting L402 offers.
The TLD .ai mandates a minimum registration and renewal period of two years. So inform the user that they need to purchase a 2 year package when they request a .ai domain.

The L402 offer structure:
{
    'offers': [
        {
            'offer_id': 'example_offer_id',  # String identifier for the offer
            'amount': 100,                 # Numeric cost value in USD cents
            'currency': 'usd',             # Currency code
            'description': 'Example offer', # Text description
            'title': 'Example Package'      # Title of the package
        }
    ],
    'payment_context_token': 'example_token',  # Payment context token
    'payment_request_url': 'https://api.example.com/payment-request',  # Payment URL
    'version': '0.2.2'  # API version
}

sid: Search ID from a previous search request
domain: Domain name to purchase from the search results related to `sid`

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
domainYes
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the return type (L402 offer), its structure, and how it can be processed ('by any tool supporting L402 offers'). It also includes important domain-specific constraints (.ai TLD requirements). However, it doesn't mention potential errors, rate limits, or authentication needs, leaving some behavioral aspects uncovered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized but not optimally structured. It front-loads the purpose but includes an extensive JSON example that could be summarized more concisely. The .ai TLD note is important but interrupts the flow. Some sentences could be tightened for better readability.

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?

Given the tool's complexity (domain purchasing with payment offers), no annotations, and no output schema, the description does a good job of explaining the return value structure and constraints. It covers the essential context needed to use the tool effectively, though additional information about error handling or authentication would make it more complete.

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?

The schema description coverage is 0%, so the description must compensate. It clearly explains both parameters: 'sid' as 'Search ID from a previous search request' and 'domain' as 'Domain name to purchase from the search results related to `sid`'. This adds crucial semantic meaning beyond the bare schema, though it could provide more detail about format constraints or examples.

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 purpose: 'Request available payment options for a domain.' It specifies the verb ('request') and resource ('payment options for a domain'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'search' or 'domains' beyond mentioning domain purchase context.

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 context by mentioning that the domain should be 'from the search results related to `sid`' and includes a note about .ai domains requiring 2-year packages. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'search' or 'domains', nor does it specify prerequisites or exclusions beyond the sid and domain parameters.

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/Fewsats/sherlock-mcp'

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