Skip to main content
Glama

Quote a domain price

quote_domain
Read-onlyIdempotent

Live price quote for one domain. Returns premium (boolean) and renewal_price (USD/yr). Premium orders are refused if they exceed what we can currently fund.

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": {
      "domain": "<domain>"
    },
    "name": "quote_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "body": {
      -      "type": [
      -        "object",
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "http_status": {
      -      "type": "integer"
      -    }
      -  },
      -  "required": [
      -    "http_status",
      -    "body"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "body": {
      +      "type": [
      +        "object",
      +        "array",
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "http_status": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "http_status",
      +    "body"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only, idempotent operation, so the description appropriately focuses on additional behavior. It discloses return fields (premium and renewal_price) and a meaningful operational constraint: premium orders are refused if they exceed currently available funds.

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 three short, front-loaded sentences with no wasted wording. The core purpose, return values, and premium-order constraint are all presented efficiently.

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?

For a read-only quote tool without an output schema, the description usefully names the key return fields and a premium-order constraint. It remains incomplete for the undocumented years parameter and does not state what happens when a domain is unavailable or invalid.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the parameters. It implies the domain parameter through 'one domain', but it never explains the years parameter, its default, or how it affects the quote.

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 a specific action and resource: a live price quote for one domain. It is clear from the name and text, but it does not explicitly distinguish the tool from siblings such as estimate_domain_value, which could also appear relevant to pricing.

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?

Usage is only implied by 'Live price quote for one domain'; an agent can infer this is for checking a purchase or renewal price before ordering. However, there is no explicit guidance on when to use this instead of estimate_domain_value, search_domains, or create_order, and no prerequisites or exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources