EneUI Catalogue

get_page

Fetch any catalog page as Markdown (a component, a category hub, a library page, an article). Use the same paths as the site, e.g. /components/cat/modal or /blog.

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

Name	Required	Description	Default
`path`	Yes	Site path, e.g. /components/cat/modal

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return format (Markdown) and that paths mirror the site, which is genuinely useful behavior. However, it says nothing about read-only nature, behavior on an invalid or missing path, auth requirements, or rate limits.

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 compact sentences with the format and scope front-loaded, followed by a concrete path convention and examples. Every clause carries information; nothing is padding.

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 no output schema, the description covers what is returned (Markdown), what page types are reachable, and how to construct the path. The remaining gap is failure behavior for bad paths, which is minor at this complexity.

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 path parameter is already documented with an example in the schema. The description reinforces the semantics by stating paths mirror site URLs and adding a second example (/blog), but adds no format rules, normalization behavior, or constraints 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 gives a specific verb and resource ('Fetch any catalog page') and explicitly enumerates the page kinds covered (component, category hub, library page, article) plus the return format (Markdown). It stops short of distinguishing itself from siblings like get_component or get_block, so an agent must infer that this is the generic path-based fetcher.

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?

'Use the same paths as the site' with two concrete examples implies how to call it, but there is no statement about when to prefer it over get_component, get_block, or compose_page, and no exclusions or prerequisites. Usage is workable but must be inferred from the sibling set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EneUI Catalogue tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?