Skip to main content
Glama
derikfernandes

BCB Payment Methods MCP Server

consultar_estabelecimentos_credenciados

Query the number of establishments authorized to accept electronic payment methods per quarter using Brazil's Central Bank data. Filter and sort results by quarter and other parameters.

Instructions

Consulta quantidade de estabelecimentos credenciados para aceitar meios de pagamento eletrônico 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)
ordenar_porNoCampo para ordenação
filtroNoFiltro OData para refinar a consulta

Implementation Reference

  • Main handler for executing the 'consultar_estabelecimentos_credenciados' tool in the MCP CallToolRequestSchema handler. Extracts parameters, calls fetchBCBData on BCB API endpoint 'EstabCredTransDA', and returns JSON-formatted data.
    case "consultar_estabelecimentos_credenciados": {
      const { trimestre, top = 100, ordenar_por, filtro } = args as {
        trimestre: string;
        top?: number;
        ordenar_por?: string;
        filtro?: string;
      };
    
      const data = await fetchBCBData(`EstabCredTransDA(trimestre=@trimestre)?@trimestre='${trimestre}'`, {
        formato: "json",
        top,
        orderby: ordenar_por,
        filter: filtro,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'consultar_estabelecimentos_credenciados' tool, defining parameters like trimestre (required), top, ordenar_por, and filtro.
    {
      name: "consultar_estabelecimentos_credenciados",
      description: "Consulta quantidade de estabelecimentos credenciados para aceitar meios de pagamento eletrônico 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)",
          },
          ordenar_por: {
            type: "string",
            description: "Campo para ordenação",
          },
          filtro: {
            type: "string",
            description: "Filtro OData para refinar a consulta",
          },
        },
        required: ["trimestre"],
      },
    },
  • Handler for 'consultar_estabelecimentos_credenciados' tool in the HTTP server's MCP createMCPServer CallToolRequestSchema switch. Identical logic to index.ts.
    case "consultar_estabelecimentos_credenciados": {
      const { trimestre, top = 100, ordenar_por, filtro } = args as {
        trimestre: string;
        top?: number;
        ordenar_por?: string;
        filtro?: string;
      };
    
      const data = await fetchBCBData(`EstabCredTransDA(trimestre=@trimestre)?@trimestre='${trimestre}'`, {
        formato: "json",
        top,
        orderby: ordenar_por,
        filter: filtro,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the tool in http-server.ts tools array, matching index.ts.
    name: "consultar_estabelecimentos_credenciados",
    description: "Consulta quantidade de estabelecimentos credenciados para aceitar meios de pagamento eletrônico 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)",
        },
        ordenar_por: {
          type: "string",
          description: "Campo para ordenação",
        },
        filtro: {
          type: "string",
          description: "Filtro OData para refinar a consulta",
        },
      },
      required: ["trimestre"],
    },
  • Helper function fetchBCBData used by the tool handler to query the BCB Olinda API, building URL with OData params and fetching JSON data.
    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;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool queries data, implying a read-only operation, but does not mention potential side effects, rate limits, authentication needs, or response format. The description lacks details on what 'quantidade' entails (e.g., counts, aggregated data) or any constraints beyond the quarterly scope.

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 front-loads the core purpose without unnecessary details. It directly states what the tool does ('Consulta quantidade...') and the key constraint ('por trimestre'), with zero wasted words, making it highly concise and well-structured.

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

Completeness2/5

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

Given the complexity (4 parameters, no annotations, no output schema), the description is incomplete. It lacks information on behavioral traits (e.g., read-only nature, potential errors), output format, or usage context relative to siblings. While the schema covers parameters, the description does not address gaps in understanding how the tool behaves or what results to expect, making it inadequate for full contextual understanding.

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 input schema has 100% description coverage, providing clear documentation for all parameters (trimestre, top, ordenar_por, filtro). The description adds no additional parameter semantics beyond implying a quarterly focus for 'trimestre', which is already covered in the schema. With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate with extra insights.

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 tool's purpose: 'Consulta quantidade de estabelecimentos credenciados para aceitar meios de pagamento eletrônico por trimestre' (Query quantity of establishments accredited to accept electronic payment methods per quarter). It specifies the verb ('Consulta'), resource ('estabelecimentos credenciados'), and scope ('por trimestre'), but does not explicitly differentiate from sibling tools like 'consultar_meios_pagamento_trimestral', which might overlap in quarterly focus.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions 'por trimestre' (per quarter), but does not clarify if this is the only temporal scope available or how it differs from monthly tools like 'consultar_meios_pagamento_mensal'. There are no explicit when/when-not instructions or named alternatives.

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