Skip to main content
Glama

Minerals

Get the pull for a listing

get_listing
Read-onlyIdempotent

Returns the pull for a ref from find_design. Applies once your person has chosen a listing or an item. For an item ref (listing/item) it returns the exact pull instruction and the license link; for a listing ref, its free items to choose from. The result also carries receipt: the one line that confirms the pull to the person. Only free items are returned; the file comes from the supplier.

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": {
      "ref": "<ref>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesA ref returned by find_design: a listing ("arc") or one of its items ("arc/button").
clientNoYour client, e.g. "Claude Code" or "Cursor", to get the pull written for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds real behavioral value beyond that by disclosing the return shape ('pull instruction and the license link', 'free items to choose from') in the absence of an output schema. It also explains that a `receipt` line is included for confirming the pull to the person, and that only free items are returned with the file coming from the supplier. Error and invalid-ref behavior remain unstated.

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?

Front-loaded with the core action, then the applicability condition, then the per-ref-type return behavior — a sensible order with no filler. The terminology ('pull', 'receipt') is domain-specific and slightly under-glossed, but each sentence carries information.

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?

With no output schema, the description takes on return-value explanation and does so adequately by enumerating what each ref type returns plus the `receipt` field. Gaps around invalid refs and how the supplier file is actually delivered keep it from being fully complete.

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 schema already describes both `ref` and `client` including examples ('arc', 'arc/button', 'Claude Code'). The description reinforces that refs originate from find_design but adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns the pull for a ref') and explicitly scopes the ref to find_design output. The description also disambiguates the two ref shapes, explaining that an item ref yields a pull instruction plus license link while a listing ref yields its free items, so an agent can distinguish this from find_design and suggest_listing without opening schemas.

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

Usage Guidelines4/5

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

'Applies once your person has chosen a listing or an item' gives a clear triggering condition and implies the upstream dependency on find_design. It lacks explicit when-not guidance or a named alternative (e.g., suggest_listing for undecided cases), which keeps it below a 5.

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.