Skip to main content
Glama

Search Amino Desk

search
Read-onlyIdempotent

Search Amino Desk's published pages on peptides and GLP-1 medications: compound entries, comparisons, guides, costs and legal status. Returns titles, URLs and snippets. Also finds brand names and seller code names mentioned on the site.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 8)
queryYesWords to search for, such as a compound, brand or topic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results are restricted to published pages (scope boundary), and the response contains titles, URLs and snippets. It omits ranking/relevance behavior and how matches on brand or seller code names surface, which keeps it from a 5.

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?

Two sentences, zero filler, front-loaded with the core purpose and scope before the secondary capability. Every clause (domain list, return shape, brand/seller-code matching) carries information an agent would act on.

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 two-parameter, fully documented read-only search with rich annotations, the description covers what is searched, what comes back, and the scope boundary. The lack of output schema is offset by the stated return fields. Missing are relevance ordering and anything about result-limit interactions, which are minor for this tool's complexity.

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 both parameters are already documented and the baseline is 3. The description adds a modest amount of meaning beyond the schema by indicating that queries can target brand names and seller code names, extending 'a compound, brand or topic' in the schema. It says nothing additional about the limit parameter or result pagination.

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 gives a specific verb ('Search') plus a precise resource and scope ('Amino Desk's published pages on peptides and GLP-1 medications'), and enumerates the content types covered (compound entries, comparisons, guides, costs, legal status). It also states the return shape (titles, URLs, snippets). It stops short of explicitly differentiating from siblings like get_page or get_compound, leaving the agent to infer that this is the discovery tool and those are retrieval-by-id tools.

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?

Usage is implied rather than stated: the domain list and the note that it 'also finds brand names and seller code names' tell the agent what kinds of queries work, which is a real hint for query formulation. However, there is no explicit when-to-use versus get_page/get_compound/list_compounds, and no when-not-to-use or prerequisite guidance.

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