Skip to main content
Glama

Bcrp Pe

by io.github.pipeworx-io
OverviewAdmin

Get Series

get_series
Read-onlyIdempotent

Time-series data from the Banco Central de Reserva del Perú (BCRP) statistics API. Pass one or more BCRP series codes joined with "-" (all must share the same frequency). Returns the series names plus aligned period/value rows. Well-known codes (verified live): PD04722MM = monetary policy reference rate (monthly %); PD04638PD = interbank exchange rate S/ per US$, sell (daily); PD04640PD = banking-system (SBS) exchange rate S/ per US$, sell (daily); PN01273PM = Lima CPI, 12-month % change / annual inflation (monthly); PM04863AA = GDP, real % change (annual). Code suffix encodes frequency: ...PD/...PD = daily, ...PM/...MM = monthly, ...AA = annual. Browse more codes at https://estadisticas.bcrp.gob.pe. Optional start/end use the period format for that frequency: daily YYYY-M-D (2026-5-28), monthly YYYY-M (2026-5), annual YYYY (2024). lang is "ing" (English, default) or "esp" (Spanish).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd period, same format as start. Requires start. Omit for latest.
langNoResponse language: "ing" (English, default) or "esp" (Spanish).
startNoStart period in the frequency's format: daily YYYY-M-D, monthly YYYY-M, annual YYYY. Omit for full history.
seriesYesOne or more BCRP series codes joined with "-", e.g. "PD04722MM" or "PD04638PD-PD04640PD". All joined codes must share the same frequency.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "series": "PD04722MM"
+  },
+  {
+    "end": "2026-5-28",
+    "lang": "ing",
+    "series": "PD04638PD-PD04640PD",
+    "start": "2026-1-1"
+  },
+  {
+    "lang": "esp",
+    "series": "PN01273PM",
+    "start": "2024-1"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds beyond that by explaining returned data (series names + rows), code encoding (frequency suffix), and example working codes, enhancing behavioral understanding without contradiction.

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?

Description is fairly long but well-structured: starts with main purpose, then code rules, examples, format details, and language info. Every sentence adds value; slightly verbose but necessary given complexity.

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?

No output schema, but description states return includes series names and aligned rows. Provides examples, frequency mapping, and URL for more codes. Lacks info on error handling or rate limits but sufficient for core use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions, but the description adds significant value by providing concrete examples, format rules (e.g., 'daily YYYY-M-D'), and real well-known codes. This far exceeds basic schema info.

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?

Description clearly states it retrieves time-series data from BCRP API, specifies exact tool use with series codes, and distinguishes itself from sibling tools which are unrelated (e.g., ask_pipeworx, deep_research). Verb 'get' + resource 'series' is specific.

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?

Provides explicit instructions for using series codes with dash-joining, frequency constraints, optional start/end formats, and language. Lacks explicit 'when not to use' or alternative tools, but context is clear given sibling list.

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

All Bcrp Pe 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.

Resources