Skip to main content
Glama

Ibge Br

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Name Frequency

name_frequency
Read-onlyIdempotent

Brazilian census name statistics. Pass a first name to get its registration frequency by decade (since 1930), optionally filtered by sex or state. e.g. name="maria". Pass name="ranking" to get the top names instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sexNoOptional filter: "M" or "F".
nameYesFirst name to look up, e.g. "maria", "joao". Special value "ranking" returns the most popular names.
decadeNoOptional decade filter for ranking, e.g. "1990", "2000".
localityNoOptional 2-digit state id, e.g. "33" (RJ), "35" (SP). Omit for whole country (BR).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "maria",
+    "sex": "F"
+  },
+  {
+    "decade": "2000",
+    "name": "ranking"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds temporal scope ('since 1930') and special behavior for 'ranking' parameter, which goes beyond annotations 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, 28 words, front-loaded with purpose and examples. Every word contributes meaning with no redundancy.

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 exists, but the description indicates the return type (registration frequency by decade or top names). While further detail on response format would be helpful, the tool's simplicity makes this adequate.

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% with descriptions for all 4 parameters, including the special 'ranking' value. The description restates these with examples but does not add new semantic meaning beyond 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 clearly states it provides Brazilian census name statistics, specifying the verb 'get' (implied) and resource 'registration frequency' or 'top names'. It distinguishes itself from sibling tools by being specific to name frequency lookup.

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?

The description gives clear usage with examples ('name="maria"', 'name="ranking"') and optional filters (sex, state, decade). It lacks explicit when-not conditions but is sufficiently specific for typical use.

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

All Ibge Br 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