Skip to main content
Glama
Sign In
theses-mcp

theses-mcp

by koprjaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

fulltext

Resolve a thesis record to downloadable full-text files in its school's repository, listing all publicly exposed documents.

Instructions

Resolve a thesis to downloadable full-text files in its school's repository.

theses.cz stores only metadata; the files live in each school's own system (mostly the IS family — is.muni.cz, is.slu.cz, vskp.vse.cz …). This follows the record to that repository and lists the documents it exposes publicly.

id_or_url: thesis code ("7lfo74"), /id/7lfo74/ or a full URL.

access is the visibility of the theses.cz copy and does NOT decide what you can download: a thesis marked "autentizovaným zaměstnancům ze stejné školy" on theses.cz is often served freely by the school's own repository, so always check files.

Each file carries label, filename and url; extensionless URLs also get confirmed and content_type from a HEAD request. An empty files plus a note means the school really does gate it (login or CAPTCHA) — a real answer, not an error.

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": {
      "id_or_url": "<id_or_url>"
    },
    "name": "fulltext"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does an excellent job. It discloses that the tool follows the record to an external repository, lists publicly exposed documents, notes that the theses.cz `access` field does not determine downloadability, and explains how to interpret file fields and empty results. This gives the agent a realistic model of what happens and what to expect.

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?

The description is relatively long but every sentence adds essential context: purpose, repository layout, parameter format, access interpretation, file structure, and edge-case handling. It is front-loaded with the main verb and resource, then elaborates in a logical order. No fluff or redundancy.

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?

Given the tool's complexity, lack of annotations, and lack of an output schema, the description is exceptionally complete. It explains the output shape (`label`, `filename`, `url`, optional `confirmed` and `content_type`), behavioral nuances (`access` is not determinative), and how to handle empty results (`note` means gated, not an error). The agent has everything needed to invoke and interpret the tool correctly.

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

Parameters5/5

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

There is only one parameter, `id_or_url`, and the schema provides no description for it (0% coverage). The description fully compensates by specifying the accepted formats: 'thesis code ("7lfo74"), /id/7lfo74/ or a full URL.' This is explicit and leaves no ambiguity about what value to pass.

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 description opens with a specific verb and resource: 'Resolve a thesis to downloadable full-text files in its school's repository.' This clearly differentiates the tool from siblings `search` and `detail` by focusing on file retrieval rather than discovery or metadata. It also explains why this tool is needed (theses.cz stores only metadata) which further cements its unique purpose.

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?

The description explains the context of use and provides actionable guidance, such as 'always check `files`' and what an empty `files` plus a `note` means. It does not explicitly name alternatives or say when not to use this tool, but the purpose is clear enough to infer that it is for fulltext resolution, while siblings handle search and detail. Overall, clear context but no explicit exclusions.

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