CriptoNoticias Brasil

Buscar

buscar

Read-onlyIdempotent

Busca histórias por palavra-chave no título, resumo, tópicos e ativos (termos em português funcionam melhor). Devolve as mais recentes com «N fontes» e link para citar. Exemplos: «Notícias sobre o Drex» · «O que se sabe do ataque ao Mercado Bitcoin?» English: Keyword search over Brazilian crypto stories (Portuguese terms work best), newest first, with citation links. Example: «Brazil bitcoin ETF news»

Input Schema

Name	Required	Description	Default
`limit`	No	Quantidade (1–20).
`query`	Yes	Termo de busca, ex.: Drex, ETF, Ledger.

Output Schema

Name	Required	Description	Default
`fonte`	No
`query`	No
`total`	Yes
`historias`	Yes
`url_busca`	No
`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"
+    },
+    "query": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "url_busca": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "total",
+    "historias",
+    "atribuicao"
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds behavior the annotations do not: results are ordered newest-first and each carries 'N fontes' plus a citation link, which matters for how an agent should cite. It still leaves the meaning of 'N fontes' and any rate/coverage limits unexplained.

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 core statement is front-loaded and every element — fields searched, ordering, return contents, examples — earns its place. The fully duplicated English paragraph is deliberate for a bilingual audience but does make the block longer than strictly necessary.

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?

The tool is a simple two-parameter search with an output schema, so the description does not need to explain return shapes; it still adds the citation-link detail. Complete enough to call correctly, with the only gap being how to choose among the sibling listing tools.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning to the query parameter: it must be a keyword, Portuguese terms retrieve better, and the examples model acceptable phrasing. The limit parameter is never mentioned in the description, though its schema text ('Quantidade 1–20') is already explicit.

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 uses a specific verb and resource ('Busca histórias por palavra-chave') and even scopes which fields are searched (título, resumo, tópicos, ativos), which plainly separates it from get_historia (single story) and listar_temas. It never names a sibling or warns about its overlap with ultimas_historias, which also returns newest-first, so the differentiation is only implicit.

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?

The two worked examples («Notícias sobre o Drex», «O que se sabe do ataque ao Mercado Bitcoin?») show exactly the kind of query that belongs here, and the note that Portuguese terms work best is genuine usage guidance that prevents a bad call. What is missing is explicit routing — nothing tells the agent to prefer get_historia for a known story id or ultimas_historias for browsing without a keyword.

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?