Skip to main content
Glama

Plos Search

plos_search
Read-onlyIdempotent

Solr-powered full-text search across all PLOS open-access journals; supports field-qualified queries (e.g. abstract:CRISPR AND title:gene), pagination, sorting, and custom field selection. Returns title, authors, journal, date, and abstract by default.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "abstract:CRISPR AND title:gene"
    },
    "name": "plos_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
flNoComma-sep fields to return.
rowsNo1-1000 (default 25)
sortNoe.g. "publication_date desc"
queryYese.g. "abstract:CRISPR AND title:gene"
startNo

Output Schema

NameRequiredDescriptionDefault
responseNo
responseHeaderNoResponse metadata from Solr

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / response / properties / docs / items / properties / abstract / items
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / response / properties / docs / items / properties / abstract / type
      Previous value: -"string"New value: +[
      +  "array"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: it discloses the Solr query dialect with a concrete syntax example, confirms pagination, sorting, and field projection are supported, and states the default returned field set.

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?

Two compact sentences, front-loaded with the capability and query dialect. The closing sentence on default return fields is somewhat redundant given an output schema exists, but it is short and helps the agent anticipate field projection trade-offs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter read-only search tool with an output schema and strong annotation coverage, the description covers the query language, scope, pagination/sorting/projection capabilities, and default result shape. The only minor gap is the undocumented start parameter, which the schema's own convention makes inferable.

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 80%, so the baseline is 3; the schema already documents fl, rows, sort, and query with examples. The description reinforces field-qualified query syntax and the default field projection, but adds no new detail on start or on rows bounds beyond the schema.

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?

"Solr-powered full-text search across all PLOS open-access journals" gives a specific verb (search), resource (PLOS journals), and scope (full-text, all journals). It does not explicitly distinguish itself from siblings like plos_article or plos_recent, so the agent must infer that this is the broad/query-language entry point.

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 by the emphasis on field-qualified queries and broad journal coverage, which suggests a free-form search tool, but there is no explicit statement of when to choose this over plos_recent or plos_article, and no prerequisites or exclusions are given.

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.