Skip to main content
Glama

search_literature_extended

Search literature across multiple fields including basename, disease, geography, method, and relevance notes. Optionally retrieve archived items.

Instructions

Search literature with optional inclusion of archived items.

Searches library_seeded table across basename, relevance_note, disease,
geography, method fields. By default excludes archived items.

Args:
    query: Search term.
    include_archived: Include items with status='archived'. Default False.
    limit: Max results. Default 20.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
include_archivedNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the search scope and archiving behavior, but does not disclose read-only nature or other traits like rate limits or side effects.

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?

The description is concise with three clear sentences and a structured docstring. Every part is purposeful and front-loaded.

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?

Given the existence of an output schema, the description adequately explains inputs and search scope. It lacks info on pagination or real-time behavior, but is sufficient for a straightforward search tool.

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?

Despite 0% schema coverage, the description includes an Args section that explains each parameter's purpose and defaults, adding significant value beyond the bare 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?

The description clearly states the tool searches literature with optional archived inclusion, specifying fields and default exclusion. However, it does not differentiate from sibling search tools like search_literature or search_library.

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 description explains default behavior and parameter defaults, but provides no guidance on when to use this tool versus alternatives. No explicit when-not-to-use or alternative mentions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server