Skip to main content
Glama

Minerals

Propose a library or tool

suggest_listing

Sends a proposal for a design library or tool to the Minerals curator. Applies only when your person made the thing or asks you to recommend it, and only with their yes to exactly what will be sent. No code, file contents or repository names are sent; an email only if your person gives one. Returns one line that says the request was sent.

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": {
      "link": "<link>",
      "what_it_is": "<what_it_is>",
      "made_by_sender": "<made_by_sender>"
    },
    "name": "suggest_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe address of the library or tool.
emailNoOnly if your person gives one, to be answered.
momentNoWhen would someone reach for this? One of: Starting, Building a section, Filling a gap, Polishing, Tuning, Sharing. Leave it out if unsure.
skip_ifNoWhen someone should not use it.
best_forNoThe job it does better than anything else.
what_it_isYesWhat it is, in a sentence or two.
goes_well_withNoUp to three refs of published listings it works well beside.
made_by_senderYestrue if your person made it, false if they are suggesting it.
install_addressNoThe address an agent pulls from, if there is one.
licence_and_freeNoIts licence, and what is free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations: it discloses consent requirements, a data-minimization guarantee (no code, file contents or repository names), that email is sent only if the person provides an address, and even the return shape of one line. readOnlyHint=false and idempotentHint=false are consistent with a non-idempotent send, so nothing conflicts.

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?

Front-loaded with the action, then constraints, then return value; four short sentences with no filler. Every clause carries an operative constraint an agent needs before calling.

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 10-parameter mutation with no output schema, the definition covers consent, data handling, optionality of email, and the return value. It leaves error conditions and what happens on a rejected or duplicate request unstated, a minor gap given how much else is covered.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds meaning the schema lacks: the email field is tied to the person's explicit consent, and the 'no code, file contents or repository names' rule tells the agent what must not be put into the free-text fields.

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: sends a proposal for a design library or tool to the Minerals curator. That is clear enough to select without opening the schema. It stops short of naming how it differs from close siblings (e.g. offer), so it falls short of a 5.

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?

Explicit preconditions are given: only when the person made the thing or asked for a recommendation, and only with their yes to exactly what will be sent. That is real when-to-use guidance, but it sets no boundary against sibling tools such as offer or report_outcome.

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.