Skip to main content
Glama

Read a page of the i22 website

i22_ai_page_read
Read-onlyIdempotent

Returns the text of one published page of the i22 website. Pass the path (e.g. /leistungen) or the full URL from an i22_ai_site_search or i22_ai_page_list result.

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": {
      "path": "<path>"
    },
    "name": "i22_ai_page_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath or URL of the page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds the meaningful qualifier that only 'published' pages are returned, but says nothing about behavior for unpublished/missing paths, response size, or truncation.

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?

Two short sentences, the return value front-loaded and the parameter guidance immediately after. Every clause carries information and nothing is redundant.

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 read tool with full annotation coverage and no output schema, the description supplies what an agent needs: what comes back, and what to pass in. Minor gaps around error cases and content limits keep it from being exhaustive.

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 coverage is 100%, so the baseline is 3; the description goes beyond the schema's 'Path or URL of the page' by giving a concrete example (/leistungen) and the origin of valid URLs. That added format and provenance guidance is genuinely useful for constructing the single argument.

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: returns the text of one published page of the i22 website. The page-level, single-page scope is clear and separable from list/search siblings, though it does not explicitly contrast with a page-detail sibling such as i22_ai_service_get.

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?

Gives clear procedural context by saying the path or URL should come from an i22_ai_site_search or i22_ai_page_list result, which tells the agent this is the follow-up step after discovery. It stops short of explicit when-not-to-use conditions or naming alternative content tools.

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