itu-mcp

Overview Schema Source Related Servers Discussions Admin

Read Resource Text

read_resource_text

Read-onlyIdempotent

Extract plain text from Ninova PDF, DOCX, or TXT files or local downloads so assistants can read lecture notes and assignments.

Instructions

Extract plain text from a Ninova PDF/DOCX/TXT (or a local path from download_resource) so the assistant can read lecture notes and assignments.

Input Schema

Name	Required	Description	Default
`url`	No
`path`	No
`filename`	No
`max_chars`	No
`save_download`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.2.1Oct 14, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "result": {
+    "additionalProperties": true,
+    "title": "Result",
+    "type": "object"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "result"
+]
```

changedOutput schema / title

Previous value: -"read_resource_textDictOutput"New value: +"read_resource_textOutput"

First observedv0.2.0Jul 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds that extraction targets Ninova resources for reading, but is silent on the max_chars truncation behavior and the file-writing side effect of save_download, which an agent would want to know.

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?

A single front-loaded sentence that states the action and the resources before the purpose clause, with no wasted words. Slightly under-specified rather than padded, which is the right failure mode here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the tool is a read operation with annotations covering safety. But with five undocumented parameters and no coverage in the schema, the description is only minimally complete for invoking it correctly.

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

Parameters2/5

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

Five parameters with 0% schema description coverage, so the description must carry the load. It only implies url/path/filename by naming formats and a local path; max_chars and save_download receive no explanation at all, leaving most semantics undocumented.

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 concrete verb ('Extract plain text') and specific resources (Ninova PDF/DOCX/TXT, or a local path), which is far more specific than a tautology. It gestures at differentiation by naming download_resource as the source of the local-path input, but does not distinguish itself from the closely related read_page sibling.

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?

The phrase 'so the assistant can read lecture notes and assignments' implies the intended context, and the mention of 'a local path from download_resource' hints at a workflow. However there is no explicit when-to-use versus read_page or when-to-prefer-url-vs-path-vs-filename guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server