Skip to main content
Glama

Little Works

get_public_share_url

Vanity /project/{slug}/ etc.

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": {
      "type": "<type>",
      "slug": "<slug>"
    },
    "name": "get_public_share_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior1/5

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

There are no annotations, so the description carries the full behavioral burden, yet it discloses almost nothing. It does not say whether the returned share URL is public or authenticated, permanent or expiring, whether it errors for missing resources, or what access it grants, so an agent cannot reason about consequences before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short and front-loaded, but brevity here reflects under-specification rather than economy. The trailing "etc." is vague filler that signals an incomplete thought rather than a polished constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-required-parameter getter with no annotations and no output schema, the description is far too thin. An agent cannot tell what the two parameters mean or what the response contains, so the definition is inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%: neither slug nor type is documented anywhere. The description minimally implies slug appears in the URL path, but it says nothing about valid type values (project, recipe, material, etc.) even though type is required and enum-free, leaving the most consequential parameter undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "Vanity /project/{slug}/ etc." never states what the tool does: there is no verb like "returns" or "builds," and the tool name get_public_share_url is left to carry almost all meaning. The URL fragment hints that a public vanity path is produced from a slug, but "etc." and the bare path pattern leave the resource and result ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance is given, no prerequisites, and no distinctions from plausible alternatives such as get_listing_by_url or get_booking_confirm_link. An agent has no basis in the description for choosing this tool over a sibling.

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.

Resources