Skip to main content
Glama

bcrp_get_latest

Fetch current data points for 1–10 BCRP economic series without a date range, returning the last N observations for present-value questions like exchange rates or policy rates.

Instructions

Get the most recent data points for 1–10 BCRP series (same frequency).

Convenience wrapper around bcrp_get_series that fetches latest data without specifying a date range, then returns only the last n_periods values.

Prefer this over bcrp_get_series when the question is "what is it now?" — today's exchange rate, the current policy rate. Use bcrp_get_series for a specific historical window, and bcrp_get_series_long for many series at once or mixed frequencies.

Results are cached on disk; n_periods accepts 1–50 and defaults to 5.

Example codes:

  • Daily rates/prices: PD04637PD, PD12301MD, PD04650MD, PD04701XD

  • Monthly monetary: PN00196MM, PN00496MM, PN00178MM

  • Quarterly growth: PN03503MQ, PN03501MQ

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "series_codes": "<series_codes>"
    },
    "name": "bcrp_get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo'esp' (Spanish) or 'ing' (English)esp
n_periodsNoNumber of most recent periods to return (1–50). Default: 5.
series_codesYesList of 1–10 BCRP series codes (same frequency)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose non-obvious behavior: this is a convenience wrapper over bcrp_get_series, results are cached on disk, and it returns only the last n_periods values. It does not discuss authentication, error behavior for invalid or mixed-frequency codes, or response shape beyond the value slice, so it stops short of full disclosure for an unannotated tool.

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?

It is front-loaded with purpose and alternative-routing before the parameter detail and example codes, and each block earns its place. There is minor redundancy — 'n_periods accepts 1–50 and defaults to 5' restates the schema bounds, which are then restated again in the schema itself — but the structure is otherwise tight.

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?

For a read-only wrapper with three flat parameters and no output schema, the description covers what matters: what is returned (last n_periods values), caching, frequency homogeneity, and how to obtain valid series codes. No output schema means return-value detail is on the description, and it addresses this only at a high level (no statement of the fields accompanying each value).

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the 'same frequency' homogeneity constraint across series_codes, the 1–50 bound on n_periods, and concrete example codes grouped by frequency (daily, monthly, quarterly) that a caller can reuse directly. Only 'language' is left entirely to the schema.

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 gives a specific verb and resource ('Get the most recent data points for 1–10 BCRP series'), states a scope constraint (same frequency), and explicitly distinguishes itself from bcrp_get_series and bcrp_get_series_long. An agent can pick it out of a six-tool sibling set without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact question this tool answers ('what is it now?'), names the two alternatives, and gives the condition that selects each: a specific historical window goes to bcrp_get_series, many series or mixed frequencies go to bcrp_get_series_long. Explicit when-to-use and when-not-to-use guidance with named alternatives.

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