Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

get_domain

Retrieve domain details by specifying the provider ID and domain ID using the UseGrant MCP Server. Simplifies domain management for providers and tenants.

Instructions

Get a domain by provider and domain ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainIdYesThe ID of the domain
providerIdYesThe ID of the provider

Implementation Reference

  • src/index.ts:152-165 (registration)
    Registers the 'get_domain' MCP tool with server.tool, providing name, description, input schema, and an inline handler function.
    server.tool(
      'get_domain',
      'Get a domain by provider and domain ID',
      {
        providerId: UgSchema.ProviderIdSchema,
        domainId: UgSchema.DomainIdSchema,
      },
      async ({ providerId, domainId }) => {
        const domain = await usegrant.getDomain(providerId, domainId);
        return {
          content: [{ type: 'text', text: JSON.stringify(domain, null, 2) }],
        };
      },
    );
  • The handler function for the get_domain tool. It takes providerId and domainId, retrieves the domain via the UseGrant SDK, stringifies it to JSON, and returns it in the MCP content format.
    async ({ providerId, domainId }) => {
      const domain = await usegrant.getDomain(providerId, domainId);
      return {
        content: [{ type: 'text', text: JSON.stringify(domain, null, 2) }],
      };
    },
  • Input schema for the get_domain tool, defining providerId and domainId parameters using Zod schemas imported from '@usegrant/sdk/schema'.
    {
      providerId: UgSchema.ProviderIdSchema,
      domainId: UgSchema.DomainIdSchema,
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits like read-only nature, error handling, authentication needs, or rate limits. It doesn't add meaningful context beyond the basic operation.

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 a single, efficient sentence with zero waste—front-loaded and appropriately sized for a simple retrieval tool. Every word earns its place.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a retrieval tool. It lacks details on return values, error cases, or behavioral context, leaving gaps despite the tool's low complexity.

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?

Schema description coverage is 100%, so the schema fully documents both parameters. The description adds no extra meaning beyond implying these IDs are required for lookup, aligning with the baseline when schema does the heavy lifting.

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 verb ('Get') and resource ('a domain'), specifying it's retrieved by 'provider and domain ID'. It distinguishes from siblings like 'list_domains' by focusing on a single domain, though it doesn't explicitly contrast with 'verify_domain' or 'delete_domain'.

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 is provided on when to use this tool versus alternatives like 'list_domains' for browsing or 'verify_domain' for validation. The description implies usage when you have specific IDs, but lacks explicit context or 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

Related 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/usegranthq/mcp-server'

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