Skip to main content
Glama

Open Economics

by io.github.felipegambettadesouza6-jpg
OverviewDiscussionsAdmin

Query official formal-employment stock and flows

get_mte_formal_employment
Read-onlyIdempotent

Retrieve revised monthly Novo Caged stock, admissions, dismissals, balance, and relative change from 2020 onward. Select exactly one official breakdown: country, region, state, or economic activity. The response preserves the MTE workbook vintage and never synthesizes state-by-industry values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclusive last month, YYYY-MM.
fromNoInclusive first month, YYYY-MM.
limitNoMaximum rows to return.
statesNoOptional official state codes when breakdown is state.
regionsNoOptional official regions when breakdown is region.
breakdownNoOfficial breakdown for the employment result.country
dataset_idYesThe official MTE Novo Caged dataset identifier.
industriesNoExact official activity IDs returned by get_mte_formal_employment_schema; empty means all activities.

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. Changed8 schema fields changed
    • addedInput schema / properties / breakdown / description
      Added value: +"Official breakdown for the employment result."
    • addedInput schema / properties / dataset_id / description
      Added value: +"The official MTE Novo Caged dataset identifier."
    • addedInput schema / properties / from / description
      Added value: +"Inclusive first month, YYYY-MM."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return."
    • addedInput schema / properties / regions / description
      Added value: +"Optional official regions when breakdown is region."
    • addedInput schema / properties / states / description
      Added value: +"Optional official state codes when breakdown is state."
    • addedInput schema / properties / to / description
      Added value: +"Inclusive last month, YYYY-MM."
    • 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

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so those need no restating. The description adds genuinely non-obvious behavior: the data is *revised* monthly, it tracks the MTE workbook vintage, and combinations (state-by-industry) are never synthesized. That is real value beyond the annotations.

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?

Three tightly packed sentences: measures/scope first, the breakdown constraint second, the fidelity caveat last. Every sentence carries information, with only minor density issues from the compound noun lists.

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?

With an output schema present, return formatting need not be described, and the description covers scope, granularity constraint, and data fidelity. The one notable omission is any pointer to the sibling schema tool that supplies the valid industry IDs, which the agent needs for the industries parameter.

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 enum for breakdown plus the state/region enums are fully documented in the schema, so the baseline of 3 applies. The description reinforces the one-breakdown-at-a-time rule but adds no syntax, defaults, or format detail beyond what the schema already states.

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?

Specific verb (retrieve) plus the exact resource and the measures returned (Novo Caged stock, admissions, dismissals, balance, relative change) with a stated time floor of 2020. It does not, however, name or distinguish itself from the sibling get_mte_formal_employment_schema, which an agent could easily confuse with this query tool.

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

Usage Guidelines3/5

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

'Select exactly one official breakdown' and 'never synthesizes state-by-industry values' give the agent a real invocation constraint. There is no explicit when-to-use/when-not guidance, and no routing to the schema sibling for valid industry IDs, so usage is implied rather than fully specified.

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