get_pageFetch any public Multilo page as clean Markdown — documentation, pricing, comparisons, blog posts, or the homepage. Accepts a path ('/pricing', '/docs/install/download') or a full multilo.com URL. Far cheaper and cleaner than fetching the HTML.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Site path or full multilo.com URL, e.g. '/pricing' or '/docs/install/download'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavior. It states the 'public' scope, output as 'clean Markdown', and a cost/quality benefit over HTML. It does not mention errors or return details, but the key behavioral traits are covered for a simple fetch tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. The purpose is front-loaded, and the second sentence adds input format and a practical comparison, both earning their place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter fetch tool with no output schema, the description provides essential context: what it does, accepted input formats, output format, and scope. It lacks explicit error handling notes, but overall it is sufficiently complete for its simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description's examples mirror the schema's explanation of 'path' and add no new semantic meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Fetch' with a clear resource ('Multilo page as clean Markdown'), and it distinguishes the tool from siblings by focusing on page content retrieval rather than listing or searching. The scope (public pages) and use cases are also stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies appropriate use cases (documentation, pricing, comparisons, blog posts, homepage) and contrasts with fetching HTML, but it does not explicitly position the tool against siblings like search_docs or list_updates. It is clear when to use it but does not state when not to.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: fetching any page, listing changelog entries, and searching documentation. There is minimal overlap since get_page is generic while search_docs is specifically for locating docs.
All tool names follow a clear verb_noun pattern: get_page, list_updates, search_docs. The naming style is uniform and predictable.
Three tools is on the smaller side but appropriate for a focused server exposing Multilo's web content. Each tool has a clear role, and the count feels neither excessive nor trivial.
The tool set covers the main use cases: accessing pages, checking updates, and searching docs. Minor gaps exist (e.g., no dedicated tool to list all docs pages), but agents can work around them using get_page.