Skip to main content
Glama

Peptency research library

Search the library

search_library
Read-only

Search compounds (name, aliases, class), mechanisms, comparisons and cited study titles. Returns slugs to pass to get_compound.

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_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFree text, for example 'GLP-1', 'BPC-157' or 'growth hormone secretagogue'

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 and openWorldHint=false, so the safety profile costs the description nothing. The description adds real behavioral context beyond that: it discloses that results are slugs (identifiers, not full records) and that matching spans multiple entity types, not just compound names.

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, both load-bearing: the first defines scope, the second defines the return value and next step. Front-loaded with the verb and resource, no filler wording.

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 one-parameter read-only search with no output schema, the description covers purpose, return shape (slugs), and downstream handoff. It omits any mention of result ordering, caps, or how relevance is determined, which is a minor but real gap.

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 'query' parameter already carries an example, so the schema does the heavy lifting. The description's enumeration of searchable fields (name, aliases, class, mechanisms, comparisons, study titles) adds some guidance on what to put in the query, but nothing on syntax, matching behavior, or result limits.

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 ('Search compounds') and enumerates the searchable domains (name, aliases, class, mechanisms, comparisons, cited study titles). The closing clause 'Returns slugs to pass to get_compound' distinguishes it from the retrieval sibling, though the relationship to list_compounds is left unstated.

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 agent can infer this is the entry point before get_compound, which is a useful workflow hint. There is no explicit when-to-use/when-not guidance and no exclusion naming an alternative such as list_compounds for browsing rather than searching.

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