Skip to main content
Glama

Read a website page

get_site_page
Read-onlyIdempotent

Readable text of a public motifyme.co page listed by list_site_pages (guides, fuel price city pages, tool pages).

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_site_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesa motifyme.co url from list_site_pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 the description's burden is lighter. It still adds genuinely new context: the return is extracted 'readable text' rather than raw HTML, and only URLs drawn from list_site_pages are valid. It stops short of noting pagination, truncation, or what happens with an invalid URL.

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 front-loaded sentence that delivers the return type, the domain restriction, and the source of valid inputs with no filler. The parenthetical page-type list is slightly enumerative but earns its place by clarifying coverage scope.

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?

With only one parameter, full schema coverage, and rich annotations, the definition supplies everything needed to call it correctly. The lack of an output schema is partly offset by the 'readable text' phrasing, though it doesn't describe size or structure of the returned text.

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 single url parameter is already documented as 'a motifyme.co url from list_site_pages'. The description echoes that constraint but adds no format, encoding, or error-handling detail 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?

The description names a specific verb+output ('Readable text of a public motifyme.co page') and scopes the resource to pages surfaced by list_site_pages, with parenthetical examples (guides, fuel price city pages, tool pages). It is clearly distinguishable from search-type siblings, though it doesn't explicitly separate itself from get_blog_post, which also returns page content.

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?

It implies the correct usage path by requiring a URL 'listed by list_site_pages', which is a useful precondition. However there is no explicit when-not guidance or statement of what to use instead for blog posts, dealers, or listings, leaving the alternative selection to inference.

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