Publish one HTML page as either an unlisted or access-key protected sandboxed share.
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | The full HTML document to publish. | |
| title | No | Optional title for the share. | |
| visibility | No | Defaults to public_unlisted. private_link returns a one-time accessKey. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description mentions 'sandboxed share' which hints at security, but does not disclose important behavioral traits such as what the tool returns, whether it requires authentication, or side effects. For a creation tool, the return value (e.g., share URL or ID) is missing.
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?
A single concise sentence that front-loads the main purpose and visibility options. However, it omits the return value, which would improve completeness without adding much length.
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?
Given no output schema, the description should explain what the tool returns. It does not, leaving a gap. The schema provides parameter details well, so the description is adequate but not fully complete for an agent to use without assumptions.
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 coverage is 100% and already describes all parameters. The description adds no new information beyond the schema (e.g., the visibility enum values are already described). Baseline of 3 is appropriate.
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 clearly states the verb 'publish' and the resource 'HTML page as a share', specifying the two visibility options (unlisted or access-key protected). It distinguishes from siblings (describe_share_html, get_public_share) which are read-only tools.
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?
No explicit guidance on when to use this tool versus alternatives. The purpose implies creation, and siblings imply reading, but no explicit when-not-to-use or prerequisites.
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 has a distinct purpose: creating a share, retrieving a guide, and fetching metadata. No overlap or ambiguity.
Most tools follow verb_noun pattern (create_share, get_public_share), but 'describe_share_html' uses a descriptive prefix instead of a straightforward verb. Minor inconsistency.
Three tools is on the lower end but still reasonable for a focused service. Each tool serves a clear need without being sparse.
The set covers creation and retrieval but lacks update, delete, or listing capabilities. Users cannot manage or remove existing shares, which is a significant gap.