Skip to main content
Glama
derikfernandes

BCB Payment Methods MCP Server

consultar_terminais_atm

Query ATM terminal statistics by quarter to analyze Brazil's Central Bank payment infrastructure data, with options to filter results and limit records.

Instructions

Consulta estatísticas sobre terminais de autoatendimento (ATM/caixas eletrônicos) por trimestre.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trimestreYesAno e trimestre no formato YYYYQ (exemplo: '20234')
topNoNúmero máximo de registros a retornar (padrão: 100)
filtroNoFiltro OData para refinar a consulta

Implementation Reference

  • Handler for the 'consultar_terminais_atm' tool. Extracts parameters, calls fetchBCBData on the 'TerminaisATMDA' endpoint with the trimestre parameter, and returns the JSON data as text content.
    case "consultar_terminais_atm": {
      const { trimestre, top = 100, filtro } = args as {
        trimestre: string;
        top?: number;
        filtro?: string;
      };
    
      const data = await fetchBCBData(`TerminaisATMDA(trimestre=@trimestre)?@trimestre='${trimestre}'`, {
        formato: "json",
        top,
        filter: filtro,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • Tool definition including name, description, and input schema for 'consultar_terminais_atm'. Requires 'trimestre' (YYYYQ format), optional 'top' and 'filtro'.
    {
      name: "consultar_terminais_atm",
      description: "Consulta estatísticas sobre terminais de autoatendimento (ATM/caixas eletrônicos) por trimestre.",
      inputSchema: {
        type: "object",
        properties: {
          trimestre: {
            type: "string",
            description: "Ano e trimestre no formato YYYYQ (exemplo: '20234')",
          },
          top: {
            type: "number",
            description: "Número máximo de registros a retornar (padrão: 100)",
          },
          filtro: {
            type: "string",
            description: "Filtro OData para refinar a consulta",
          },
        },
        required: ["trimestre"],
      },
    },
  • Shared helper function to make API requests to the BCB Olinda service, builds URL with OData params and fetches JSON data. Used by all tool handlers including consultar_terminais_atm.
    async function fetchBCBData(endpoint: string, params: QueryParams = {}) {
      try {
        const url = buildUrl(endpoint, params);
        const response = await axios.get(url, {
          headers: {
            "Accept": "application/json"
          }
        });
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Erro ao consultar API do BCB: ${error.message}`);
        }
        throw error;
      }
    }
  • Helper function to construct OData query URLs for BCB API endpoints, appending parameters like $top, $filter, etc. Used by fetchBCBData.
    function buildUrl(endpoint: string, params: QueryParams = {}): string {
      const url = new URL(`${API_BASE_URL}/${endpoint}`);
    
      if (params.formato) url.searchParams.append("$format", params.formato);
      if (params.top) url.searchParams.append("$top", params.top.toString());
      if (params.skip) url.searchParams.append("$skip", params.skip.toString());
      if (params.filter) url.searchParams.append("$filter", params.filter);
      if (params.orderby) url.searchParams.append("$orderby", params.orderby);
    
      return url.toString();
    }
  • src/index.ts:263-267 (registration)
    Registers the handler for ListToolsRequestSchema, which returns the tools array including 'consultar_terminais_atm'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Consulta' implies a read-only operation, it doesn't specify whether this is a real-time query, historical data lookup, or if there are rate limits, authentication requirements, or data freshness considerations. The description lacks behavioral details beyond the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that immediately communicates the core functionality. There's no wasted verbiage or unnecessary elaboration, making it optimally concise while still being informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a query tool with 3 parameters and no output schema, the description adequately covers the basic purpose but lacks information about return format, data structure, or error conditions. With no annotations and no output schema, the description should ideally provide more context about what statistics are returned and in what format.

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 has 100% description coverage, so all parameters are documented in the schema itself. The description mentions 'por trimestre' which aligns with the required 'trimestre' parameter, but adds no additional semantic context beyond what's already in the schema descriptions. This meets the baseline for high schema coverage.

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 clearly states the action ('Consulta' - query/consult) and the resource ('estatísticas sobre terminais de autoatendimento'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools that also query different types of financial data, though the ATM terminal focus is distinct.

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?

The description provides no guidance on when to use this tool versus the sibling tools, nor does it mention any prerequisites or alternative scenarios. It simply states what the tool does without contextual usage information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/derikfernandes/bcb-meios-pagamento-mcp_2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server