Skip to main content
Glama

Read a page

get_page
Read-onlyIdempotent

The text of one page of 313automations.com as Markdown.

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

Input Schema

NameRequiredDescriptionDefault
pathYesThe page address or path, for example /services, /web-wordpress, /blog/ai-agent-cost or https://313automations.com/about. Use / for the home page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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, so the safety profile is covered. The description adds real value by disclosing the return format (Markdown text), which matters since there is no output schema. It says nothing about error behavior for bad paths or whether page chrome/navigation is included.

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?

A single short sentence with zero filler, and the essential fact (Markdown page text) is front-loaded. It is a verbless fragment, which makes it terse to the point of being slightly under-specified rather than optimally structured.

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

Completeness3/5

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

With one fully documented parameter and complete annotations, most of the burden is already carried by structured fields, and the description covers the return format. Gaps remain around behavior on missing/redirected paths and whether the output includes the whole rendered page, which an agent calling this would want to know.

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 coverage is 100% and the path parameter already documents accepted forms with concrete examples and the '/' home-page convention. The description adds no parameter meaning beyond the schema, 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 resource (one page of 313automations.com) and the return format (Markdown), which is more than a restatement of the name. It implicitly contrasts with list_pages and search_site by saying 'one page', but never names those siblings explicitly, so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus search_site, list_pages, or get_company_info, and no prerequisites or failure conditions mentioned. The only signal is the implied 'fetch a specific known page' from the word 'one page'.

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