Skip to main content
Glama
Sign In
mcp-isap

mcp-isap

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_act_text

Read-onlyIdempotent

Retrieve the full text of a Polish legal act by its ELI identifier. Returns the first 5000 characters of plain text and a link to the complete HTML or PDF document for verification.

Instructions

Pobiera tekst aktu w formacie HTML (jesli dostepny). Zwraca pierwsze 5000 znakow czystego tekstu (bez tagow) plus link do pelnego HTML/PDF. Uzywaj po get_act zeby ocenic czy akt jest tym, czego szuka uzytkownik.

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": {
      "eli": "<eli>"
    },
    "name": "get_act_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
eliYesELI aktu, np. 'DU/2018/1000'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations are already strong (readOnlyHint, idempotentHint, destructiveHint). The description adds that it returns first 5000 chars of plain text and a link, which is helpful behavioral context. No contradictions.

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?

Two sentences efficiently convey purpose and usage guidelines without waste. Front-loaded with the primary action.

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 simple retrieval tool with one parameter, complete annotations, and no output schema, the description fully covers what is returned and when to use it.

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?

Schema coverage is 100% with a clear description for the single 'eli' parameter. The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 retrieves the text of an act in HTML format, returning first 5000 characters of plain text plus a link to full HTML/PDF. It also specifies usage after get_act, distinguishing it from sibling tools get_act and search_acts.

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?

Explicitly instructs to use after get_act to evaluate if the act is what the user searches for, providing clear context for when and why to use this tool.

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