Skip to main content
Glama

Fetch an Omni Creator public page

fetch_public_page
Read-onlyIdempotent

Fetch a public Omni Creator page as markdown (or llms.txt as plain text). Allowed paths are the live directory pages. Does not call login or generation APIs.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPublic path such as /, /pricing, /use-cases/background-replace, /image-upscale, /llms.txt, or /llms-full.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds meaningful context beyond those annotations by stating the output format, restricting paths to live directory pages, and clarifying that login and generation APIs are not invoked.

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?

The description is three short sentences, front-loads the primary action, and wastes no words. Each sentence adds a useful constraint or clarification.

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 simple read-only fetch tool with full parameter schema coverage and annotations covering safety characteristics, the description is nearly complete. It could specify behavior for invalid or disallowed paths, but no output schema exists and the return format is already mentioned.

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?

The input schema has 100% description coverage and already provides path examples. The description reinforces the allowed path scope and output format but does not add substantial syntax or error-handling detail beyond the schema.

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 and resource: fetching a public Omni Creator page, with markdown or llms.txt output. It does not explicitly distinguish this from sibling tools like get_overview or list_pages, so it is clear but lacks direct sibling differentiation.

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?

The description implies usage for allowed live directory paths and notes that it does not call login or generation APIs. However, it gives no explicit when-to-use guidance, exclusions, or alternatives to the sibling 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.