Skip to main content
Glama

critics.press

ler_texto

Read-onlyIdempotent

A full critics.press piece: text (Markdown), byline, editor, sources, the "same fact, many lenses" pages, licence and a ready citation. Pass the URL or the slug. O texto inteiro, com fontes, lentes, licença e citação.

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": {
      "url": "<url>"
    },
    "name": "ler_texto"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe piece URL (https://critics.press/pt/...) or its slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds genuinely useful behavioral context beyond that by disclosing the payload shape (full Markdown body plus byline, sources, licence, ready citation), which is the main thing an agent needs to know before calling. It stops short of mentioning auth, rate limits, or error cases.

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?

The valuable content — what the piece includes — is front-loaded in a single dense clause, and the input instruction follows immediately. The trailing Portuguese sentence largely repeats the same information ('o texto inteiro, com fontes, lentes, licença e citação'), which is mild redundancy rather than waste, since it does add 'whole text'.

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 must characterize the return value, and it does so in detail by listing every component of the piece including the ready citation. What remains unstated is trivial for a single-parameter read-only fetch — chiefly the response envelope (raw Markdown vs. structured JSON) and failure behavior for bad slugs.

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?

There is a single parameter with 100% schema description coverage that already explains the URL-or-slug duality. The description's 'Pass the URL or the slug' merely restates that, adding no format examples or edge-case handling. Baseline 3 is appropriate when the schema carries the semantics.

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 enumerates exactly what a returned piece contains (Markdown text, byline, editor, sources, lens pages, licence, citation), which tells an agent this is a full-article fetch rather than a listing. The retrieval verb is only implicit ('A full critics.press piece'), and mentioning the 'same fact, many lenses' pages inside the payload could momentarily blur the line with the o_mesmo_fato sibling, but overall the resource is unmistakable.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for pulling one complete article, and 'Pass the URL or the slug' tells it what input is needed. There is no explicit statement of when to prefer it over buscar_textos or o_mesmo_fato, and no note on what happens with an invalid or ambiguous slug.

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