Skip to main content
Glama

critics.press

ultimos_textos

Read-onlyIdempotent

The latest critics.press pieces in one language (title, subtitle, genre, byline, date, URL). Os textos mais recentes do critics.press numa língua.

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": "ultimos_textos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoDefault 10, max 30.
linguaNopt, en or es (default pt).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds genuine context by stating that results are constrained to a single language and by listing the fields returned, but it says nothing about result ordering, truncation, or what happens when a language has no content.

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-loaded and short, with the resource and return fields stated first. The second sentence is a near-verbatim Portuguese restatement that carries no additional information, which is the only wasted space.

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?

For a two-parameter, optional-arg, read-only listing tool with no output schema, the description covers what it returns and the language scoping. Ordering and pagination beyond the limite cap are left implicit, but nothing critical to correct invocation is missing.

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%, with limite (default 10, max 30) and lingua (pt/en/es, default pt) fully documented in the schema. The description only reinforces the single-language constraint already implied by the lingua enum, adding no new syntax or semantics, so baseline 3 applies.

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?

Names a specific resource (critics.press pieces) with a clear scope modifier (latest) and enumerates the returned fields (title, subtitle, genre, byline, date, URL), so an agent knows this is a recent-items listing. It does not explicitly contrast itself with buscar_textos or ler_texto, which keeps it from a 5.

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 when-to-use guidance and no mention of alternatives; the only signal is the word 'latest' in the description. An agent must infer for itself that this is the browse-recent path rather than the search or read-single-text paths offered by siblings.

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