Skip to main content
Glama

mt_get_text

Read-onlyIdempotent

Fetch the complete text of Maltese legislation using an ELI coordinate, retrieving the official PDF content directly from the legislation.mt portal.

Instructions

Fetch the full text of a Maltese document by ELI coordinate (from the official PDF).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eliYesthe coordinate after ``/eli/`` (e.g. ``"cap/586"``).
langNo``"eng"`` (default) or ``"mlt"``.eng

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eliNo
titleNo
formatNotext/plain (extracted from the official PDF)
contentNo
eli_uriNo
pdf_urlNo
byte_sizeNo
text_noteNoMalta publishes the consolidated text only as PDF; mt_get_text downloads the official PDF and extracts the text with pypdf. Layout-dependent artefacts are possible - the PDF at source_url (via the page) is authoritative.
source_urlNo
dataset_noteNolegislation.mt serves consolidated Maltese law addressed by ELI coordinate: chapters (cap/{number}), the Constitution (const), subsidiary legislation (sl/{chapter}.{number}), Acts (act/{year}/{number}) and Legal Notices (ln/{year}/{number}). Metadata comes from the page's schema.org/ELI JSON-LD; the full text is only available as a PDF. There is no free-text search here - address documents by their ELI coordinate. Languages: English (eng) and Maltese (mlt).
human_readable_citationNo
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, establishing safe read behavior. The description adds the source ('official PDF') and scope ('full text'), which gives minor context beyond safety. However, it does not disclose error behavior, language output, or any caching aspects, but the annotation coverage lowers the burden.

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?

A single, front-loaded sentence that conveys the core functionality without wasted words. It is appropriately sized for the tool's simplicity.

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?

The tool is simple, has an output schema, and its annotations cover safety. The description communicates the source and output type sufficiently. It lacks explicit alternative guidance, but that is more a usage-guideline concern; overall it is complete enough for invocation.

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?

The schema covers both parameters with descriptive text (eli coordinate, lang values), and the description's mention of 'by ELI coordinate' reinforces eli's role. Since schema description coverage is 100%, the description adds little beyond schema, meriting the baseline 3.

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 clearly states the tool fetches the full text of a Maltese document using an ELI coordinate, specifying the source as the official PDF. The verb 'Fetch' and resource 'full text' make the purpose unambiguous, and the sibling tool name (mt_get_act) suggests a different focus, providing implicit differentiation.

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 description implies usage for retrieving document text but provides no explicit when-to-use or alternative guidance. It does not explain when to prefer this over mt_get_act, leaving the agent to infer which tool matches the user's intent. No exclusions or context is given beyond the basic purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matematicsolutions/mt-eli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server