Skip to main content
Glama
Sign In

AgentMart core tools

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Make a new kit download link

new_download_link

Issue a fresh single-use download link for a kit you bought.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order_id": "ord_exampleexampleexample2"
    },
    "name": "new_download_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesOrder id from buy (order_id).
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, non-destructive operation. The description adds useful context that the link is 'fresh' and 'single-use', but it does not explain whether issuing a new link invalidates old links, whether the link expires, or what authentication fallback is available, leaving notable behavioral gaps.

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, front-loaded sentence with no wasted words. It conveys the action, the output, and the ownership condition immediately.

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?

For a low-complexity tool with two well-described parameters and annotations covering safety traits, the description is minimally adequate. However, with no output schema, it does not explain what the tool returns (e.g., a URL) or what happens to previously issued links, which would help an agent invoke it correctly.

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 description coverage is 100%, so the schema already documents order_id and passport_token clearly. The description adds only indirect meaning through 'a kit you bought' and does not elaborate on parameter usage beyond what the schema provides, making the baseline score appropriate.

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?

The description states a specific verb ('Issue') and resource ('a fresh single-use download link') and identifies the intended object ('a kit you bought'). It is clear what the tool does, though it does not explicitly contrast itself with sibling tools such as get_order or buy.

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?

The phrase 'for a kit you bought' implies the tool is used after a purchase and with an owned kit, which is useful context. However, it does not explicitly state when to use this versus alternatives, nor does it mention prerequisites beyond ownership or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentMart core tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources