Skip to main content
Glama

Pandawed — Chinese flashcards (HSK)

Статьи блога Пандаведа

list_articles
Read-onlyIdempotent

Опубликованные статьи блога pandawed.ru о китайском языке и HSK: адрес (slug), заголовок, описание, дата.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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=false, so the safety profile is fully covered. The description adds one useful behavioral fact beyond that — only published articles are returned — but says nothing about ordering, pagination or result-set size, which matters for a parameterless listing tool.

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 scope first and then itemizes returned fields, with no filler. It is as short as it can be while still carrying the field list, which is needed because no output schema exists.

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, enumerating the returned fields (slug, title, description, date) is the essential missing piece and it is supplied, along with the published-only filter. For a zero-parameter list tool this is nearly complete; only ordering and pagination behavior remain unspecified.

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?

The tool takes zero parameters at 100% schema coverage, so there is nothing for the description to disambiguate; baseline 4 applies. The field enumeration in the description describes output, not input, and thus neither helps nor hurts this dimension.

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?

The description names the specific resource (published articles of the pandawed.ru blog about Chinese and HSK) and enumerates the fields returned (slug, title, description, date), so the agent knows exactly what this tool yields. It does not explicitly contrast itself with search_articles or get_article, so sibling differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as search_articles for filtered lookups or get_article for a single full article. The word 'Опубликованные' hints that drafts are excluded, but that is scope, not routing guidance.

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.

Resources