Skip to main content
Glama
Sign In
uleszka

uleszka

by jokerwader
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Opracowanie artykułu

get_article_notes
Read-only

Retrieve AI-prepared notes for an article, including a summary, verified quotes for main theses, topics, people, places, dates, and cited sources to review or compare claims quickly.

Instructions

Returns the AI-prepared notes for an article: summary, the author's main theses (each with a verbatim quote verified to occur in the article), topics, people, places, dates/periods and sources the author cites. Use it for a quick overview or to compare the author's claims with current knowledge. Notes are an AI aid, not part of the original website.

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": "<id>"
    },
    "name": "get_article_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid albo tytuł artykułu

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real behavioral context beyond that: notes are AI-generated aids rather than original website content, and quotes are verified to occur verbatim in the article. That provenance and reliability caveat materially affects how an agent should present the output.

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, front-loaded with what is returned, then the use cases, then the caveat. The content enumeration is dense but every item is informative and there is no filler.

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?

With no output schema, the description must describe the return payload, and it does so item by item. Combined with the AI-aid disclaimer and the readOnly annotation, an agent has everything needed to call and interpret it correctly.

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 description coverage is 100% and the single parameter is documented as 'id albo tytuł artykułu', so the schema carries the load. The description adds nothing about the parameter (e.g. whether a title match must be exact), leaving this at the baseline.

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 specific verb and resource ('Returns the AI-prepared notes for an article') and enumerates exactly what those notes contain: summary, theses with verbatim quotes, topics, people, places, dates and sources. This is far more precise than a sibling like read_article would imply, though it never names a sibling to draw the contrast explicitly.

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?

'Use it for a quick overview or to compare the author's claims with current knowledge' gives concrete situations that select this tool. It stops short of an explicit exclusion (e.g. 'use read_article for the full text'), so the agent must infer the boundary from sibling names alone.

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