Skip to main content
Glama

Get site overview

get_site_overview
Read-only

Fetch the public nake.si homepage to retrieve its title, meta description, and up to 20 internal HTTPS links; no image or video generation calls.

Instructions

Fetch only the public homepage https://nake.si/ and return its title, meta description, and up to 20 https links on nake.si. Does not call image or video generation APIs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope detail — that it is a single fixed URL, that links are capped at 20 and restricted to https, and that no image or video generation APIs are invoked. It says nothing about failure modes, redirects, or rate limits, which is a real gap for an open-world network call.

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?

Two front-loaded sentences with the target URL and return fields stated first. The closing sentence about image/video APIs is somewhat defensive and non-obvious in origin, but it plausibly preempts a wrong assumption about the tool's capability, so it roughly earns its place.

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 parameters and no output schema, the description carries the burden of explaining results, and it does — naming the three returned fields and the 20-link cap. For a zero-arg tool this is close to complete; only error/edge behavior and the sibling boundary are unaddressed.

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 the schema baseline is 4 and there is no parameter meaning to add. The description correctly supplies no parameter text and instead spends its words on scope and return content.

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?

States a specific verb ('Fetch'), a precise resource (the public homepage at https://nake.si/), and the exact payload returned: title, meta description, and up to 20 https links on nake.si. That is far more than a restatement of the name. It stops short of naming the sibling read_public_page, so the boundary with it is left implicit.

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?

'Fetch only the public homepage' signals this is a fixed-site, fixed-page tool rather than a general fetcher, which implies read_public_page is the path for other pages. However, that alternative is never named and no when-not condition is stated explicitly, so the agent must infer the routing.

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

Deploy Server

Other Tools