Skip to main content
Glama
p-pouget

watch-materials-mcp

by p-pouget

last_articles_arxiv_materiaux

Retrieve recent materials science preprints from ArXiv sorted by date, covering emerging works not yet peer-reviewed.

Instructions

Récupère les derniers PREPRINTS parus en science des matériaux sur ArXiv (tous matériaux confondus, sans filtre), triés par date. Couvre les travaux émergents non encore validés par les pairs. Pour cibler un matériau précis, utiliser le tool de recherche ArXiv par matériau. Pour des articles PUBLIÉS en revues, utiliser les tools OpenAlex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoNombre d'articles récents à retourner (défaut 30)
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the 'no filter' and sorting behavior but lacks details on pagination, rate limits, or any side effects. Since it's a read-only fetch, the missing info is not critical but still leaves gaps.

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?

Two concise sentences, front-loaded with purpose and followed by usage guidelines. No unnecessary words or repetition.

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?

Tool is simple with one optional parameter and no output schema. Description explains what is returned (list of preprints sorted by date) but does not describe the output format or fields. Slight gap but not severely incomplete.

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

Parameters3/5

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

Schema coverage is 100% for the single parameter maxResults, which already includes a description. Description does not add any additional meaning beyond the schema, so baseline 3 applies.

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?

Description clearly states verb 'Récupère', resource 'PREPRINTS', domain 'science des matériaux', and sorting by date. Distinguishes from siblings like search_arxiv_materiaux (specific material search) and last_articles_openalex_materiaux (published articles).

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 tells when to use (emerging works) and when not to (for specific material, use search; for published articles, use OpenAlex tools). No ambiguity.

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/p-pouget/watch-materials-mcp'

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