Skip to main content
Glama

Send feedback to Paper Nexus

submit_feedback

Send the Paper Nexus team a short note about this service. Reports on its data are the most useful: a title, author list, year, venue, DOI or link that is wrong, a record that is really a different paper, citations or references that look off, or a paper, field or source the user needed and Paper Nexus doesn't have. Errors, timeouts, confusing tool descriptions or results, and features the user wished for are welcome too. Send one when the user asks to, or when you notice a problem with a Paper Nexus result, and tell the user what you sent. Say what you expected and what came back, and pass the papers it is about (Paper Nexus ids, links or DOIs) in papers. Leave out personal details, and the user's own text beyond what the report needs. A note changes no result now and gets no reply in this conversation; an account may send 10 a day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "message": "<message>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoThe Paper Nexus tool the note is about, if one is
papersNoThe papers it is about, as Paper Nexus ids or links, DOIs, arXiv ids or titles; kept as given
messageYesThe note: what happened, what you expected and what came back. 10 to 2000 characters
categoryYesWhat the note is about: wrong_data: a title, author, year, venue, DOI, link, citation or reference that is wrong, or a record that is a different paper; missing_data: a paper, field or source the user needed that Paper Nexus does not have; bug: an error, a timeout, a broken link or a result that failed; feature_request: something the user wished Paper Nexus did; tool_usability: a tool description, argument or result that was confusing or hard to use; other: anything else

Output Schema

NameRequiredDescriptionDefault
categoryYes
receivedYes
feedback_idYesThe note's reference, if the user asks
remaining_todayYesNotes this account may still send today

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=false, idempotent=false, openWorld=false; the description adds substantive context beyond that — no immediate effect on results, no reply in this conversation, a 10-per-day per-account cap, and a privacy constraint to omit personal details. These are operational facts an agent cannot infer from the schema.

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?

Purpose is front-loaded, followed by report content, triggers, content guidance, and constraints, in a sensible order. It runs long and partly duplicates the category enum's listing of report kinds, but nearly every sentence carries actionable instruction.

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?

For a low-risk submission tool with a fully documented schema and an output schema, the description covers everything an agent needs: what to send, when, what to tell the user, privacy limits, rate limits, and the absence of a reply. Nothing material is missing.

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 baseline is 3, and the description earns an increment by reinforcing how to fill `papers` (Paper Nexus ids, links or DOIs) and what `message` should contain ('what you expected and what came back'). It does not restate the `tool` or `category` enums, which the schema already documents thoroughly.

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 gives a specific verb and recipient ('Send the Paper Nexus team a short note about this service') and immediately enumerates what a useful note contains, so the agent knows exactly what this tool produces. It is plainly distinct from the query-oriented siblings like search_papers or verify_references.

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?

It states both trigger conditions explicitly: 'when the user asks to, or when you notice a problem with a Paper Nexus result', and adds a follow-up obligation ('tell the user what you sent'). It also sets the negative expectation that a note changes nothing now and gets no reply, which prevents the agent from waiting on a response.

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