Skip to main content
Glama

Search publications

search_publications
Read-onlyIdempotent

AND-filtered bibliography, newest first. Keyword includes PDF text and returns match snippets. citation_format returns citations per page; export links every match as one file. Cite amira_url.

Input Schema

NameRequiredDescriptionDefault
typeNoExact type; discover values with list_publication_facets
limitNoDefault 25; max 100 summaries or 25 exports, also byte-bounded
venueNoJournal/book title, partial
authorNoAuthor/editor name, either name order
exportNoReturn a file link instead of rows
offsetNo
keywordNoTitle, abstracts, venue, subjects or full text; every word must match, quote a phrase
subjectNoSubject heading, partial
year_toNo
languageNoLanguage name or ISO code
year_fromNo
added_sinceNoAdded to AMIRA on or after this ISO date
has_fulltextNoFilter by extracted full-text availability
citation_formatNoOmit for summaries; pages carry bibtex, ris or csl_json

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / added_since
      Added value: +{
      +  "description": "Added to AMIRA on or after this ISO date",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / author / maxLength
      Added value: +1000
    • changedInput schema / properties / citation_format / description
      Previous value: -"Omit for summaries; export results contain bibtex, ris or csl_json"New value: +"Omit for summaries; pages carry bibtex, ris or csl_json"
    • addedInput schema / properties / export
      Added value: +{
      +  "description": "Return a file link instead of rows",
      +  "enum": [
      +    "csv",
      +    "jsonl",
      +    "bibtex",
      +    "ris",
      +    "csl-json"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / keyword / description
      Previous value: -"Title, abstract, venue, subjects or full text; substring match"New value: +"Title, abstracts, venue, subjects or full text; every word must match, quote a phrase"
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
    • addedInput schema / properties / language / maxLength
      Added value: +1000
    • addedInput schema / properties / subject / maxLength
      Added value: +1000
    • addedInput schema / properties / type / maxLength
      Added value: +1000
    • addedInput schema / properties / venue / maxLength
      Added value: +1000
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: newest-first ordering, keyword matching against PDF full text with snippet returns, per-page citations under citation_format, and a single consolidated export file.

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?

Four short sentences, front-loaded with the filter/sort semantics and then the three output-shaping modes. Dense and largely waste-free, though 'Cite amira_url' is a fragment whose referent is unclear.

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 14-parameter read tool with no output schema, the description covers sort order and the three output modes (summaries, per-page citations, export file). Pagination/limit behavior is left entirely to the schema, but the core invocation-affecting behavior is present.

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?

Schema coverage is high (79%) and the description still adds meaning beyond it: keyword reaches PDF text and returns match snippets, citation_format yields per-page citations, and export collapses every match into one file link. These clarify the interaction between parameters rather than restating field definitions.

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 names the resource (bibliography/publications) and the operation (AND-filtered search, newest first), which is more specific than the title 'Search publications'. It narrows scope usefully but does not explicitly distinguish itself from siblings like search, search_research_items, or list_publication_facets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this tool versus alternatives, nor any exclusions. The schema points at list_publication_facets for discovering type values, but the description never routes the agent to siblings such as compare_collections or get_publication.

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.