Skip to main content
Glama

search_reports

Read-onlyIdempotent

Search transportation research reports by keywords in titles, abstracts, subjects, authors, or report numbers, with filters for year, collection, document type, and source.

Instructions

Search titles, abstracts, subjects, authors and report numbers across all sources.

Args:
    query: Keywords. Quote phrases ("driver improvement"); trailing * = prefix;
        column prefixes work: title:pedestrian, authors:lynn, report_numbers:"813 097".
    year_min / year_max: Inclusive publication-year filter.
    collection: Substring filter on collection name (see list_collections), e.g. "NHTSA",
        "VTI", "BASt", "World Bank", "CEPAL", "TRID", "PubMed".
    doc_type: Substring filter on document type, e.g. "Tech Report", "Dataset".
    source: Comma-separated id prefixes to restrict to, e.g. "dot,vti" (dot = ROSA-P,
        vti, bast, wbokr, ipea, cepal, openalex, cinii, pubmed, trid).
    limit: Max hits (1-100). offset: for paging.
    mode: "hybrid" (default: keyword BM25 fused with semantic vectors when an embedding
        index exists), "keyword", or "semantic" (meaning-based, cross-language). Semantic
        results are capped at 50% from any one source unless `source`/`collection` is
        set; use `source` to search one corpus by meaning. ``mode_used`` says what ran.
Returns ranked hits; ``match_mode`` says whether all query terms matched (all_terms),
the hit came from the any-term fallback, or from the semantic index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNohybrid
limitNo
queryYes
offsetNo
sourceNo
doc_typeNo
year_maxNo
year_minNo
collectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important runtime behavior: hybrid mode fuses BM25 with semantic vectors, semantic results are capped at 50% from one source, mode_used reports which mode actually ran, and match_mode distinguishes all_terms, any-term fallback, and semantic matches. This is rich, non-obvious behavioral context.

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 structured as a clear Args list with the purpose front-loaded. It is dense but not wordy, and every sentence adds necessary information such as syntax rules, examples, source mappings, and mode behavior. The length is justified by 9 parameters and no schema-level descriptions.

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?

Given the complexity of this search tool, the description covers all parameters, syntax variants, behavioral caveats, and output signals like match_mode and mode_used. An output schema exists, so return-value documentation is not required in the description. Nothing needed to invoke the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description documents every parameter in detail: query syntax with examples, inclusive year filters, substring semantics for collection/doc_type, comma-separated source prefixes with corpus mappings, limit bounds, offset for paging, and mode semantics. It fully compensates for the schema's lack of descriptions.

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?

The opening sentence names a specific verb ('Search'), a clear resource ('titles, abstracts, subjects, authors and report numbers'), and scope ('across all sources'). It distinguishes this from siblings like search_fulltext, which presumably searches full text, and from lookup/find_similar, which are different operations.

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

Usage Guidelines4/5

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

The description gives extensive usage guidance: query syntax, quoting, prefix wildcards, column prefixes, date filtering, collection/source filtering, mode selection, and paging. It does not explicitly name alternatives or state when not to use this tool, but the context is clear enough for an agent to decide when search_reports is appropriate.

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/aquistbe/transport-lit'

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