papserMCP_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONGODB_URI_READONLY | Yes | A read-only MongoDB URI for the portal's database. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_papersC | Search for question papers from CodeChef VIT Papers Portal using filters. Caps results at 20. |
| get_paper_metadataA | Retrieve complete metadata for a specific question paper by its ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent-papers | A read-only feed of the last 10 papers added to the database. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches for papers using filters, the other retrieves metadata for a specific paper by ID. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern: 'search_papers' and 'get_paper_metadata'. The naming is clean and predictable.
With only 2 tools, the server is on the thinner side, but they cover the core search-and-retrieve flow. It feels slightly under-scoped for a question paper portal, but not unreasonable.
The server covers searching and fetching metadata, but it lacks an operation to download or access the actual paper content. Depending on the metadata, this may be workable, but it is a notable gap for a paper-focused server.