Skip to main content
Glama

AICTIONBOT™ Werkbank

Read one article, practice case or method page from the KULIC Advisory library as text

get_article
Read-onlyIdempotent

KULIC Advisory library (Dario Kulic). Returns the text of one published page or one signal read from the library, with its headings, the source and the link. Pass the path from search_library, for example /insights/governance-decision-rights/ for an article or /insights/#s-01 for a signal read (any of the six languages). Only entries of the library can be read, not arbitrary addresses. The text is the page as published; quote it with the source and the link. No AI, no sign-in, nothing stored.

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": {
      "path": "<path>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath or full link of the page as returned by search_library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), yet the description still adds real context: no sign-in required, nothing is stored, scope is restricted to the library domain, and the six-language coverage. It omits one thing that matters for a text-read tool — whether long pages are returned whole or truncated — which keeps it off a 5.

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?

Front-loads the purpose, then the input, then the constraint, then the output contract — a sensible order with no filler sentences. Minor slack in the parenthetical attribution '(Dario Kulic)' and the slightly staccato closing triad, but nothing that costs comprehension.

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?

With no output schema, the description carries the return-value burden and does so (headings, source, link), and it covers the single required parameter and the domain restriction. For a one-parameter read tool with full annotation coverage this is nearly complete; only the handling of oversized pages is unaddressed.

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

Parameters4/5

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

Schema coverage is 100% and the single param is documented, so the baseline is 3; the description earns extra credit by supplying concrete path examples and clarifying that either a bare path or a full link is acceptable. It does not explain how fragments ('#s-01') map to signal reads beyond the example, so it is additive rather than exhaustive.

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?

States a specific verb and resource — 'Returns the text of one published page or one signal read' — and enumerates what comes back (headings, source, link). It also differentiates itself from the sibling search_library by requiring the path that tool returns, so an agent can route correctly without opening either schema.

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?

Gives an explicit precondition ('Pass the path from search_library'), concrete path shapes for both content types ('/insights/governance-decision-rights/' and '/insights/#s-01'), and an explicit exclusion ('Only entries of the library can be read, not arbitrary addresses'). Nothing about when to reach for get_article versus other siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.