CriptoNoticias Brasil

Últimas histórias

ultimas_historias

Read-onlyIdempotent

Últimas histórias de cripto no Brasil (pt-BR), da mais nova para a mais antiga. Cada história agrupa a mesma notícia de vários veículos e traz «N fontes», resumo, datas e o bloco citacao (texto + link para citar). Use para «o que aconteceu hoje». Filtro opcional por tag (tópico ou ativo: Bitcoin, Ethereum, Brasil, Mercados, Política e Regulação). Exemplos: «O que aconteceu hoje com cripto no Brasil?» · «Últimas notícias de regulação» English: Latest Brazilian crypto stories, newest first, each grouped from N outlets, with a ready citation (text + link). Use for 'what's new today'; optional tag filter. Example: «What's new on Ethereum in Brazil?»

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

Input Schema

Name	Required	Description	Default
`tag`	No	Tópico ou ativo, ex.: Bitcoin, Ethereum, Brasil, Mercados, Política e Regulação.
`limit`	No	Quantidade (1–20).

Output Schema

Name	Required	Description	Default
`tag`	No
`fonte`	No
`total`	Yes
`historias`	Yes
`atribuicao`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "atribuicao": {
+      "properties": {
+        "como_citar": {
+          "type": "string"
+        },
+        "dados": {
+          "type": "string"
+        },
+        "detalhes": {
+          "type": "string"
+        },
+        "how_to_cite": {
+          "type": "string"
+        },
+        "licenca": {
+          "type": "string"
+        },
+        "text_en": {
+          "type": "string"
+        },
+        "texto": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "texto",
+        "licenca"
+      ],
+      "type": "object"
+    },
+    "fonte": {
+      "type": "string"
+    },
+    "historias": {
+      "items": {
+        "properties": {
+          "ativos": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "atualizado_em": {
+            "properties": {
+              "brasilia": {
+                "type": "string"
+              },
+              "iso": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "iso",
+              "brasilia"
+            ],
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "citacao": {
+            "properties": {
+              "fontes_originais": {
+                "type": "string"
+              },
+              "texto": {
+                "type": "string"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "texto",
+              "url"
+            ],
+            "type": "object"
+          },
+          "citar_como": {
+            "type": "string"
+          },
+          "n_fontes": {
+            "type": "integer"
+          },
+          "publicado_em": {
+            "properties": {
+              "brasilia": {
+                "type": "string"
+              },
+              "iso": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "iso",
+              "brasilia"
+            ],
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "resumo": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "story_id": {
+            "type": "string"
+          },
+          "tipo": {
+            "type": "string"
+          },
+          "titulo": {
+            "type": "string"
+          },
+          "topicos": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "type": "string"
+          },
+          "veiculos": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "story_id",
+          "titulo",
+          "n_fontes",
+          "slug",
+          "url",
+          "citacao"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tag": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "historias",
+    "atribuicao"
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: stories are ordered newest first, each groups the same news item from multiple outlets, and results include “N fontes,” summary, dates, and a citation block with text and link.

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 definition is front-loaded with the Portuguese description and then mirrors it in English, which doubles length but remains clear and structured. The sentences are purposeful, though the bilingual repetition is somewhat verbose for an agent-facing definition.

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 low-complexity latest-stories tool with an output schema and full schema coverage, this is nearly complete: it covers purpose, ordering, grouping, citation output, use case, and the optional tag filter. The main gap is that it does not route the agent relative to sibling tools like buscar or get_historia.

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%, so both parameters are already documented. The description mentions the optional tag filter and gives example tags, but those examples duplicate the schema; it does not discuss the limit parameter in prose. Baseline 3 is appropriate because the schema carries parameter 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 states a specific resource and scope: latest Brazilian crypto stories, newest first, grouped by story with sources, summary, dates, and citation block. It is clear what the tool returns, but it does not explicitly differentiate itself from sibling tools such as buscar or get_historia.

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?

It gives a clear use case — “Use para «o que aconteceu hoje»” — and examples such as “Últimas notícias de regulação” and “What's new on Ethereum in Brazil?”. It also notes the optional tag filter, but does not state when not to use it or name alternative sibling tools for other retrieval needs.

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

All CriptoNoticias Brasil tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?