get_public_share
Fetch public metadata for a Share HTML slug.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Public Share HTML slug |
Share HTML
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description should carry the full burden of behavioral disclosure. It only states 'Fetch public metadata' which implies a safe read operation, but it does not disclose any potential limitations, rate limits, authentication requirements, or what 'public' exactly means.
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 a single, concise sentence that immediately conveys the tool's purpose without any wasted words. It is front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description is functionally complete. However, it lacks details about the return format or what constitutes public metadata, which would be helpful for an agent with no prior context.
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% for the single parameter 'slug', which is documented as 'Public Share HTML slug'. The description adds no extra meaning beyond restating the resource type, so it meets the baseline but does not enhance understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Fetch' and the resource 'public metadata for a Share HTML slug'. It distinguishes from sibling tools: 'create_share' is for creation and 'describe_share_html' likely provides more detailed information, while this tool is specifically for public metadata.
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?
No explicit guidance on when to use this tool versus alternatives. The description implies it is for fetching public metadata, but does not clarify when to prefer it over 'describe_share_html' or how it relates to 'create_share'.
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.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool has a distinct purpose: creating a share, retrieving a guide, and fetching metadata. No overlap or ambiguity.
Naming Consistency4/5
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.
Tool Count4/5
Three tools is on the lower end but still reasonable for a focused service. Each tool serves a clear need without being sparse.
Completeness2/5
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.