Skip to main content
Glama

site_detail

Retrieve page details from a Westlake site URL, including title, body summary, and downloadable attachments limited to *.westlake.edu.cn.

Instructions

点进一条站内页面取详情:标题 / 正文摘要 / 附件下载(仅 *.westlake.edu.cn)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "site_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes条目页绝对 URL(来自 site_content)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose one important constraint — attachments only from *.westlake.edu.cn — but says nothing about authentication needs, whether the page is fetched live or cached, or what happens with off-domain URLs or unreachable pages.

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 compact sentence with the action front-loaded and the returned fields and domain restriction listed after. No filler or redundancy.

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 single-parameter reader with no output schema, the description usefully previews the return payload (title / summary / attachments) and flags the domain restriction. Only the failure behavior for non-westlake or broken URLs is left unstated.

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% and the single 'url' parameter is already documented as an absolute item-page URL sourced from site_content. The description adds no further syntax or format meaning, so the baseline 3 applies.

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 and resource ('点进一条站内页面取详情') and enumerates what comes back: title, body summary, attachment download. That makes it distinguishable from the listing/search siblings such as site_content and site_search, though the description itself never names those siblings.

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?

The intended flow is only implied: the schema note '来自 site_content' signals this is the follow-up call after a listing, but the description gives no explicit when-to-use or when-not-to-use rule, nor any statement that list-level tasks should go to site_content/site_search instead.

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