Astro Docs MCP

只读冒烟测试 / 通过

Find Astro's public documentation for file-based routing.

这是一项使用固定输入的直接工具测试，不涉及 AI 模型或 ChatGPT、Claude 会话。调用尝试数可能包含报错或超时的调用。

The response passed the registered content assertions.

冒烟测试工具调用尝试数

1

工具

search_astro_docs

场景与版本

astro-routing-docs / 1

观察时间

2026-10-15T07:18:10.350Z

测试程序

1.0.0

协议

2025-06-18

耗时

597 ms

运行 ID

c832174f-a4ba-4e3f-b0b3-10dc0fea5858

结果 SHA-256

c1bfa2445c77bc0a09168bd87b307f2e73bf1c96b4381a91ac711b2e96c00ce0

准确的公开输入

{
  "query": "Astro file based routing src/pages"
}

固定场景断言

• routing: 通过
• src/pages: 通过

{
  "search_results": [
    {
      "content": "# En > Guides\n## Routing\n\nAstro uses **file-based routing** to generate your build URLs based on the file layout of your project `src/pages/` directory.\n\n### Navigating between pages\n\nAstro uses standard HTML [`<a>` elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a) to navigate between routes. There is no framework-specific `<Link>` component provided.\n\nsrc/pages/index.astro\n\n```\n<p>Read more <a href=\"/about/\">about</a> Astro!</p>\n<!-- With `base: \"/docs\"` configured --><p>Learn more in our <a href=\"/docs/reference/\">reference</a> section!</p>\n```\n\n### Static routes\n\n`.astro` [page components](https://docs.astro.build/en/basics/astro-pages/) as well as Markdown and MDX Files (`.md`, `.mdx`) within the `src/pages/` directory **automatically become pages on your website**. Each page’s route corresponds to its path and filename within the `src/pages/` directory.\n\n```\n Example: Static routessrc/pages/index.astro        -> mysite.com/src/pages/about.astro        -> mysite.com/aboutsrc/pages/about/index.astro  -> mysite.com/aboutsrc/pages/about/me.astro     -> mysite.com/about/mesrc/pages/posts

• One fixed public read-only request from a direct MCP client. No model selection, ChatGPT/Claude host, OAuth, private account or write behavior was tested.
• Content assertions check the listed literal terms and absence of a tool error; they do not establish complete factual correctness, relevance or production reliability.
• Observed call duration is one sample and includes network conditions. It is not a latency benchmark or a comparison between services.
• Only the first tools/list page is inspected for this selected tool. No notification stream, redirect, credentials or caller-supplied scenario is allowed.
• Response SHA-256 covers the UTF-8 JSON serialization of the SDK-parsed tool result. Only a bounded public text excerpt is retained; it is untrusted server content.