Skip to main content
Glama

Meelion MCP

by io.github.danmarkprintes

Projecoes futuras de indices (Meelion)

get_future_projections
Read-only

Retorna projeções futuras agregadas por ano para Selic, DI (CDI), IPCA ou dólar (câmbio / Focus), conforme dados atualizados pela Meelion (mesma base que a API /api/indicadores/projecoes-futuras). Informe indice ou index com um dos valores: selic, di, ipca, dolar, cambio. Use quando o usuário perguntar sobre expectativas de juros, inflação futura, mercado implícito em DI, projeção do Copom, curva implícita ou cenário macro para renda fixa. English keywords: future Selic, DI futures curve, IPCA expectations, FX expectations, Focus report, implied rates, year-ahead inflation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anoNoAno civil para filtrar um único ponto da série; se omitido, retorna todo o período disponível.
yearNoAlias em inglês de "ano".
indexNoAlias em inglês de "indice" (obrigatório se indice omitido).
indiceNoSlug do índice (obrigatório se index omitido): selic, di, ipca, dolar ou cambio (sinônimo de dólar).

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive behavior. The description adds useful context about the data source (Meelion) and points to the underlying API endpoint, as well as noting the aggregation by year. No contradictions with annotations.

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 description is three sentences plus a keyword list, front-loaded with the core purpose, then parameter instruction, then use cases. It is dense but each sentence contributes meaningful guidance, with no wasteful filler.

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 description provides purpose, data source, aggregation level, and clear usage scenarios. While it doesn't detail the response fields, the phrase 'projeções futuras' and the mention of the API endpoint give a sufficient high-level understanding for an agent to decide whether to use the tool.

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?

The schema provides 100% coverage with descriptions for all parameters, including the alias relationships and the implicit requirement that one of 'indice' or 'index' be provided. The description simply restates this guidance without adding new semantic information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns year-aggregated future projections for Selic, DI, IPCA, or dollar, referencing the Meelion API endpoint. It distinguishes itself from siblings by focusing on future projections and explicitly naming the data source.

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 description explicitly lists when to use the tool (e.g., expectations for interest rates, future inflation, implied DI market, Copom projection, implied curve, macro scenario for fixed income) and includes English keywords. It does not mention exclusions or alternative tools, but the context is specific enough to guide selection.

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

All Meelion MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource: best investments, current indicators, future projections, specific investment details, and market quotes. The descriptions clearly separate current from projected indicators, and list vs. detail views. No overlapping functionality.

Naming Consistency5/5

All tools follow a consistent 'get_' prefix with descriptive noun phrases in snake_case. This creates a predictable pattern where the resource is always clear from the name.

Tool Count5/5

With 5 tools, the server is well-scoped for a financial information provider. Each tool addresses a core need without redundancy or bloat.

Completeness5/5

The tool surface covers the full read-only workflow: discover best investments, inspect details, check current indicators, view future projections, and monitor market quotes. No obvious gaps for the stated purpose of Brazilian fixed income and economic data.

Resources