Skip to main content
Glama

Open Economics

by io.github.felipegambettadesouza6-jpg
OverviewDiscussionsAdmin

Inspect Novo Caged dimensions and measures

get_mte_formal_employment_schema
Read-onlyIdempotent

Inspect the official adjusted Novo Caged selection contract, source vintage, measure meanings, available industry IDs, and the constraint that geography and industry come from separate official tables. Use before an industry query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataset_idYesThe official MTE Novo Caged dataset identifier.

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: +"The official MTE Novo Caged dataset identifier."
    • 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.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real informational value: source vintage, measure meanings, available industry IDs, and the cross-table geography/industry constraint, which the agent would not know from annotations alone.

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?

Two tight sentences with no filler; the list of returned contents is efficiently packed and the usage cue is placed last. Minor density of domain jargon keeps it from a 5.

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?

An output schema exists, so return values need not be re-explained. The description covers purpose, contents, and usage adequately for a single-const-param introspection tool, leaving only minor gaps (no sibling routing).

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?

Single parameter with 100% schema description coverage; the const dataset_id is fully explained by the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (Inspect) and resource (Novo Caged selection contract) and enumerates the contents returned (measure meanings, industry IDs, constraints). It is clearly distinguishable from the sibling get_mte_formal_employment, though the phrase 'selection contract' is somewhat jargon-heavy.

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?

Gives an explicit usage condition: 'Use before an industry query.' That is actionable timing guidance, but it names no alternative and offers no when-not-to-use clause, so it falls short of the 5 level.

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