Skip to main content
Glama
aidvizhhub

camoufox-research

by aidvizhhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Поиск статей

paper_search
Read-onlyIdempotent

Search scientific papers across arXiv and Semantic Scholar to return primary sources with year, authors, and citations, optionally using Crossref or Wikipedia.

Instructions

Поиск научных статей: arXiv + Semantic Scholar (бесплатные API, без ключей). Возвращает статьи с годом/авторами/цитатами — первоисточники (tier 0), которых общий поиск почти не видит (паттерн индустрии: vertical index / arxiv-канал рядом с вебом). Кэш на сутки. sources — какие индексы брать (arxiv/semantic/ crossref/wiki); пусто — arxiv+semantic. Пример: paper_search("deep research agents", sources=["arxiv"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
sourcesNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.21.1
    • addedInput schema / properties / sources / anyOf
      Added value: +[
+  {
+    "items": {
+      "enum": [
+        "arxiv",
+        "semantic",
+        "crossref",
+        "wiki"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sources / default
      Previous value: -"arxiv,semantic"New value: +null
    • removedInput schema / properties / sources / type
      Removed value: -"string"
  2. Addedv0.18.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/no-destructive, so safety is covered. The description adds real behavioral context beyond them: no API keys needed, results include year/authors/citation counts, and a one-day cache that affects freshness of repeated queries.

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?

Front-loaded with the core action, then defaults, then an example — a sensible order. Some parenthetical industry commentary ('паттерн индустрии: vertical index…') is filler that could be trimmed without losing information.

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?

An output schema exists, so return values need not be spelled out, and the description still summarizes the shape (year/authors/citations). Combined with the documented sources semantics and cache behavior, an agent has enough to call this correctly; only max_results remains unaddressed.

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 description coverage is 0%, so the description carries the load. It documents sources effectively (allowed values arxiv/semantic/crossref/wiki, default behavior, and an example), but max_results and the query field are left entirely to the schema, so it doesn't fully compensate for the gap.

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+resource ('Поиск научных статей') and enumerates the two backends (arXiv + Semantic Scholar). It explicitly contrasts its scope with general search ('которых общий поиск почти не видит'), letting an agent distinguish it from the web_search sibling without opening any schema.

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?

Gives clear operating context: free APIs without keys, 24h cache, and how to select indexes via sources with defaults (empty = arxiv+semantic) plus a concrete example call. It does not name web_search explicitly as the alternative to avoid, so routing is implied rather than stated.

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

Deploy Server

Other Tools