Skip to main content
Glama

Read a page

get_page
Read-onlyIdempotent

Fetch the full text of one aidata.stream page as Markdown. Accepts a path ("/pricing/", "/docs/getting-started/") or an absolute aidata.stream URL. Use list_pages or search_site to find URLs.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage path or absolute URL on aidata.stream.
max_charsNoTruncate the Markdown after this many characters. Use a small value when tool output is size-capped.

Output Schema

NameRequiredDescriptionDefault
urlYes
markdownYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_chars / default
      Added value: +40000
    • changedInput schema / properties / max_chars / description
      Previous value: -"Truncate the Markdown after this many characters (default 40000)."New value: +"Truncate the Markdown after this many characters. Use a small value when tool output is size-capped."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by stating the return format is Markdown and that both page paths and absolute URLs are accepted.

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?

Three short sentences, front-loaded with the core action and return format, followed by accepted input forms and discovery alternatives. Every sentence adds useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-page read tool with an output schema and rich annotations, the description covers purpose, accepted inputs, return format, and URL-discovery alternatives. Nothing an agent needs in order 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?

Schema description coverage is 100%, so the schema already documents both parameters well. The description adds concrete path examples such as "/pricing/" and "/docs/getting-started/" plus the absolute-URL alternative, giving meaning beyond the bare schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: fetch the full text of one aidata.stream page as Markdown. It distinguishes the tool from list_pages and search_site by making clear this reads a single known page, and it specifies the accepted input forms.

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 explicitly directs the agent to list_pages or search_site when it needs to find URLs, which gives clear alternative-tool guidance. It does not spell out when-not-to-use cases or error conditions, but the usage context is otherwise clear.

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