Skip to main content
Glama

arXiv Papers: Newest in Robotics

arxiv__recent-cs-ro
Read-onlyIdempotent

The newest arXiv submissions in cs.RO (Robotics). Costs $0.002 USDC per call via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arxiv__recent-cs-ro"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults, max 50 (default 25)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 openWorld, so the safety profile is covered. The description adds genuinely useful non-annotation context: a per-call cost of $0.002 USDC via x402, which affects how freely an agent calls it. No rate limits or result freshness window are given.

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 tight sentences with zero waste: purpose first, cost second. Nothing redundant or padded.

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 one-optional-param tool with an output schema and rich annotations, the description covers purpose, category scope, ordering ('newest') and cost. It need not explain return values since an output schema exists; only freshness/pagination nuance is left implicit.

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 description coverage is 100% and the single 'limit' parameter (max 50, default 25) is fully documented in the schema. The description adds nothing about limit semantics, so the baseline of 3 applies.

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?

States a specific verb+resource with an explicit scope: 'newest arXiv submissions in cs.RO (Robotics)'. The category label is what distinguishes it from the dozen recent-* siblings, so an agent can route correctly, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'newest submissions' – fetch the latest robotics papers – but there is no when-to-use vs when-not guidance and no pointer to arxiv__search or arxiv__recent for broader queries. Adequate but not explicit.

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.

Resources