Skip to main content
Glama

Open Economics

by io.github.felipegambettadesouza6-jpg
OverviewDiscussionsAdmin

Inspect a SICONFI fiscal report

get_siconfi_schema
Read-onlyIdempotent

Get the meaning and required selection fields for an exact SICONFI dataset returned by search_official_data. Use this before get_siconfi_data so entity, reporting period, report type, government branch, and annex are explicit rather than guessed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesExact SICONFI dataset ID returned by search_official_data.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesSource-preserving data or schema payload for the selected official dataset.
metaYesResponse metadata and source provenance.
linksNoRelated API links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dataset_id / description
      Added value: +"Exact SICONFI dataset ID returned by search_official_data."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "description": "REST-aligned Open Economics response with data, metadata, links, and source provenance.",
+  "properties": {
+    "data": {
+      "description": "Source-preserving data or schema payload for the selected official dataset."
+    },
+    "links": {
+      "additionalProperties": {},
+      "description": "Related API links.",
+      "properties": {
+        "observations": {
+          "description": "Canonical observations endpoint for this dataset.",
+          "type": "string"
+        },
+        "self": {
+          "description": "Canonical URL for this response.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "meta": {
+      "additionalProperties": {},
+      "description": "Response metadata and source provenance.",
+      "properties": {
+        "dataset": {
+          "description": "Open Economics dataset identity when supplied."
+        },
+        "provenance": {
+          "description": "Upstream source URLs, versions, timestamps, and methodology details."
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "meta"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent read (readOnlyHint, idempotentHint, openWorldHint=false), so the safety profile is covered. The description adds real context: it discloses that the fields surfaced are the selection dimensions needed downstream and that the ID must come from search_official_data, though it says nothing about error behavior on a non-matching ID.

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?

Two tight sentences: the first defines the tool, the second gives the workflow rule. Nothing is padding, and the purpose is front-loaded.

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

Completeness5/5

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

With an output schema present, return values need not be explained; the description covers purpose, provenance of the input, and sequencing. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100% and the single parameter's description ('Exact SICONFI dataset ID returned by search_official_data') already conveys format and source. The description largely restates that same guidance, so the schema does the heavy lifting — baseline 3.

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?

States a specific verb (Get) and resource (meaning and required selection fields for an exact SICONFI dataset), and ties it to the sibling that produces the ID (search_official_data) and the sibling it precedes (get_siconfi_data). An agent can distinguish it from the other *_schema and get_*_data tools without opening a 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?

Explicitly says to use it before get_siconfi_data and explains why (so entity, period, report type, branch, and annex are explicit rather than guessed). That names both the alternative and the condition that selects it.

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

All Open Economics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources