Skip to main content
Glama

Sunset Website MCP

site_info

Read-onlyIdempotent

What Sunset (sunsetmixing.com) is, with links to its sitemap, docs, contact and every discovery document.

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": "site_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is fully covered structurally. The description adds what the payload contains (links to sitemap, docs, contact, discovery docs), which is real value, but it says nothing about format, size, or whether the links are absolute URLs — relevant since there is no output schema.

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?

A single sentence with no filler, and the identifying detail (Sunset / sunsetmixing.com) is front-loaded. The phrasing is a slightly awkward sentence fragment, but every clause contributes information about the return contents.

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?

For a zero-parameter discovery tool with no output schema, the description carries the burden of saying what comes back, and it does list the link categories returned. It would be fully complete if it noted this is the recommended first call for navigating the site, but nothing an agent needs to invoke it correctly is missing.

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. Baseline 4 applies; the description neither misleads about inputs nor wastes space on nonexistent arguments.

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 names the concrete resource (site info for Sunset / sunsetmixing.com) and enumerates what it surfaces: sitemap, docs, contact, and discovery documents. It is clearly distinct from siblings like read_page or search_pages because it is an index/discovery surface rather than a content fetch. It loses a point only for being phrased as a noun fragment rather than an explicit verb+resource statement and for never naming the siblings it differs from.

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?

There is no explicit 'use this when' instruction, but 'every discovery document' implies it is the entry point for orienting on the site before calling read_page or search_pages. No alternatives or exclusions are stated, so the agent must infer the routing. Minimum viable, not helpful guidance.

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