Skip to main content
Glama

Aevia

by ai.aeviamodeler
OverviewDiscussionsAdmin

Search literature

knowledge_search
Read-onlyIdempotent

Search 130,000+ peer-reviewed sustainability papers and the account's uploads. Articles from Sustainability, the Journal of Cleaner Production, the International Journal of Life Cycle Assessment and the Journal of Industrial Ecology, 1993 to the present — LCA, material flows, energy, food and agriculture, materials, waste, buildings and policy. English-language; most entries are abstract and metadata only. Returns ref-numbered metadata only (title, authors, year, journal, DOI) — no abstract, no excerpts. Refs (e.g. k1, k7) persist for this session and are accepted by knowledge_get_excerpts (passages) and knowledge_get_full_document (the full paper). limit defaults to 12; a larger limit suits broad literature surveys. Optional filters: journal (its full name) and year_from / year_to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default: 12). Bump toward 30 for broad literature surveys.
queryYesSearch query. The library is English-language: technical terms and scientific names match best.
journalNoOptional. Restrict the search to ONE journal, by its full name (e.g. "Journal of Cleaner Production"). A distinctive fragment also works ("Cleaner Production"), but a fragment matching several journals is rejected with the candidates listed — never guessed at — so prefer the full name. To compare journals, run one search per journal. Omit to search every document this session can reach — including the user's own uploads and anything else with no journal recorded, which a journal filter would exclude.
year_toNoOptional inclusive upper bound on publication year. Omit for no upper bound.
year_fromNoOptional inclusive lower bound on publication year (e.g. 2020 for "recent"). Omit for no lower bound.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search query"New value: +"Search query. The library is English-language: technical terms and scientific names match best."
  3. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / year_from / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / year_from / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / year_to / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / year_to / minimum
      Added value: +-9007199254740991
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description adds substantial context beyond them: returns are metadata-only with no abstracts or excerpts, refs persist only for the session, coverage is English-language and abstract-heavy, and journal-fragment ambiguity is rejected with candidates rather than guessed. This is genuinely useful behavioral disclosure.

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?

Front-loaded with corpus and scope, then returns, then ref lifecycle and downstream tools, then parameters — every sentence carries distinct information despite the density. No filler or redundancy.

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?

With no output schema, the description carries the return-value burden and does so precisely (ref-numbered title/authors/year/journal/DOI only), plus session-scoped ref persistence. For a 5-parameter, read-only search tool this is complete.

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 100%, so the baseline is 3, and the description earns an increment by tying parameters to intent: limit default 12 with 'a larger limit suits broad literature surveys', year_from/year_to as optional bounds, and journal as a full-name single-journal restriction. Most of this restates the schema, so it does not reach 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (130,000+ peer-reviewed sustainability papers plus account uploads), scopes the corpus by journal and date, and implicitly distinguishes itself from the sibling retrieval tools it hands refs to. An agent can tell this apart from knowledge_get_excerpts and knowledge_get_full_document without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the downstream alternatives — refs are 'accepted by knowledge_get_excerpts (passages) and knowledge_get_full_document (the full paper)' — and the journal filter guidance states when to omit it and why (it would exclude uploads and unjournaled docs). Conditions for larger limits and per-journal comparison searches are also given.

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

All Aevia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources