Skip to main content
Glama
OOBE-PROTOCOL

SAP MCP Server

sap_sns_check_domain

Check whether a .sol domain name is available for registration. Determine domain availability before purchasing.

Instructions

Check whether a .sol domain is available for registration using the SAP SDK SnsModule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoThe .sol domain name to check for availability (with or without .sol suffix)
Behavior2/5

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

No annotations provided, so description must disclose behavior. It fails to state whether this is a read-only operation, whether it requires authentication, or what the return format is. A simple 'check' implies no side effects, but explicit statements are missing.

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?

One clear, front-loaded sentence with no filler. Every word is necessary.

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 tool is simple (1 parameter, no output schema), but the description lacks details on expected output type (boolean?) and error scenarios. Adequate for the basics but not fully complete.

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 coverage is 100% and the description adds no new meaning beyond the schema's description (whether to include .sol suffix is already in schema). Baseline score of 3 applies.

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?

The description uses a specific verb ('Check') and resource ('.sol domain availability'), clearly distinguishing the action from siblings like batch check or resolve.

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 the batch variant (sap_sns_batch_check_domains) or any prerequisites. The mention of 'using SAP SDK SnsModule' is irrelevant for an AI agent.

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/OOBE-PROTOCOL/sap-mcp'

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