Skip to main content
Glama

Niche of One Network

Download

get_download
Read-onlyIdempotent

Members. Get a 10-minute download link for one product this member owns.

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": {
      "product": "<product>"
    },
    "name": "get_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct slug or title, as my_library lists it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does: the returned link expires in 10 minutes and the product must already be owned. Link expiry is a genuinely non-obvious operational trait. It omits what the failure mode looks like when the product isn't owned.

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?

Two short sentences with the access constraint first and the action second; nothing is wasted. The bare 'Members.' fragment is efficient but slightly telegraphic compared with a full clause.

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 conveys the returned artifact (a download link), its lifetime, and the ownership prerequisite — enough to call it correctly. Only the not-owned or expired-link behavior is left unstated.

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 parameter's own description ('Product slug or title, as my_library lists it') already tells the agent which identifier to supply. The prose adds only the ownership constraint, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get a 10-minute download link') scoped to 'one product this member owns,' which separates it from library-listing siblings like my_library or read_library. It stops short of naming a specific alternative tool, so it is clear but not fully differentiated.

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?

'Members' and 'this member owns' imply a membership and ownership precondition, which is implicit when-to-use guidance. It never explicitly says when to use this instead of read_library or my_library, nor what to do if the member does not own the product.

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