Skip to main content
Glama

Peptency research library

Get cited studies

get_studies
Read-only

Studies cited in the library with PMID, DOI, design and what each measured. Filter by compound, by words in the title, or both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional words to match in the title or what was measured
compoundNoOptional slug, name or alias

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 safety is covered; the description goes further by disclosing the actual return fields (PMID, DOI, design, measured), which matters because no output schema exists. It omits limits, pagination, or how complete the cited-study set is, so it is not fully transparent.

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 tight sentences: the payload is front-loaded, then the filtering options. Nothing is redundant or padded.

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 simple two-optional-parameter read tool with annotations and no output schema, the description covers both what is returned and how to filter. Missing only edge context such as default behavior when unfiltered and result-size limits.

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 explains both parameters, including that query matches title or measured outcome. The description adds only the 'or both' combination semantics, and it slightly narrows 'query' to title-only wording that the schema contradicts.

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 resource — studies cited in the library — and enumerates the payload fields (PMID, DOI, design, measured outcome), so the agent knows exactly what comes back. It does not differentiate itself from the sibling search_library, which is the main gap.

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 clause 'Filter by compound, by words in the title, or both' implies when the tool is useful and that filters are optional, but it never says when to prefer this over search_library or get_compound, nor what happens with no filters at all.

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