SiteMinder MCP Server and API by Cotlet

Close dates in SiteMinder

siteminder_close_dates

Read-onlyIdempotent

Close dates in the user's own SiteMinder account from ChatGPT, Claude or any AI agent. Returns how to do it in SiteMinder step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's SiteMinder Cloud Browser. SiteMinder's official API: SiteMinder has APIs, but the ones that change rates, availability and restrictions or deliver reservations are for technology partners who sign a partnership agreement and certify each API (checked 11 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "siteminder_close_dates"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint/non-destructive annotations, the description discloses the return shape (step-by-step screens, buttons, fields), explicitly denies side effects ('opens nothing by itself'), and explains why no official API path exists (partner agreement plus per-API certification). That rationale prevents an agent from wasting calls looking for an API-based alternative.

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

Conciseness4/5

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

The behavioral distinction is front-loaded in the first sentence, and the follow-up path comes before the vendor context. The API-partnership sentence is longer than strictly necessary but earns its place by pre-empting a wrong turn toward the official API.

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?

With no output schema, the description correctly explains what comes back (step-by-step UI instructions) and what the tool will not do. The remaining gap is that it never says what inputs the agent should collect conversationally (dates, property/channel) given the empty schema, which would matter for a zero-parameter action.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is fully self-describing. Baseline 4 applies; the description does not need parameter guidance.

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 verb and resource (close dates in SiteMinder) and immediately clarifies the surprising part: this tool does not perform the action, it returns step-by-step UI instructions. The contrast with the actual execution path (cotlet_browser_* tools) makes the tool's role clear without opening any schema.

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?

It gives clear usage context: call this to get the screens/buttons/fields, then follow through with the cotlet_browser_* tools in the SiteMinder Cloud Browser. It also implicitly excludes expecting a mutation here ('opens nothing by itself'). It does not compare against sibling SiteMinder API tools like siteminder_update_inventory or siteminder_update_rates, so an agent must infer the boundary itself.

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

All SiteMinder MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?