Skip to main content
Glama
Sign In

Invokely official statistics

by io.github.estevecastells
OverviewDiscussionsAdmin

Profile of a place

get_place_profile
Read-onlyIdempotent

An overview of one place in a single call: its latest official figures grouped in sections (people, work and income, economy, prices and housing, consumers, business and tourism, health, digital, energy and environment), each with its period, its change from a year earlier, its rank among similar places and its source, plus a one-sentence summary per section. Use it for "give me an overview of Travis County", "key statistics for Bavaria", "a profile of Mataró". For one figure use get_value; for a ranking use rank_places. Only sections the place has data for are returned, with at most 6 figures each. sections limits the answer to some of them: people, work_income, economy, prices_housing, consumers, business, health, digital, environment. Example: {"place": "Travis County, Texas"}. {"place": "Spain", "sections": ["economy", "work_income"]}. Returns {place, url, sections: [{id, title, summary, figures: [{indicator, value, text, period, status?, change?: {kind, value, unit, from_period, from_value}, change_note?, rank?: {rank, counted_from, of, tied, period, among, ranking_url}, source}]}], sources: [{id, name, publisher, title, url, retrieved, license, citation}], notes}. change.kind is percent, points (percentage points), difference or compare (a net balance, given with the earlier value). rank counts from the nearer end: {rank: 3, counted_from: "lowest"} is the 3rd lowest. Each figure names its source by id; cite sources[].citation and give the period. One call, whatever the number of figures.

Input Schema

NameRequiredDescriptionDefault
placeYesPlace name or id. Examples: "Mataró", "Barcelona", "provincia de Barcelona", "Cataluña", "España", "Germany", "EU", "es-mun-08121", "08121" (INE code), "ES51" (NUTS), "Texas", "Travis County, Texas", "us-county-48453", "fips:48453" (US county FIPS), "Austin, TX", "us-place-4805000", "fips:4805000" (US city GEOID).
countryNoOptional ISO 3166-1 alpha-2 code to disambiguate the place, for example "ES" or "US".
sectionsNoOptional. Sections to return; all by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sections / items / enum
      Previous value: -[
-  "people",
-  "work_income",
-  "economy",
-  "prices_housing",
-  "business",
-  "health",
-  "digital",
-  "environment"
-]New value: +[
+  "people",
+  "work_income",
+  "economy",
+  "prices_housing",
+  "consumers",
+  "business",
+  "health",
+  "digital",
+  "environment"
+]
    • changedInput schema / properties / sections / maxItems
      Previous value: -8New value: +9
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context beyond them: only sections with data are returned, at most 6 figures per section, one call regardless of figure count, and the semantics of change.kind values and rank counting direction. This is exactly the extra detail annotations cannot express.

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?

Front-loaded with purpose, then triggers, then alternatives, then parameter and return detail. It is long, and the change.kind/rank enumeration leans into output documentation, but with no output schema that detail is largely load-bearing rather than padding.

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?

For a 3-parameter read tool with no output schema, the description supplies the complete response shape (sections, figures, sources, notes) plus the value semantics an agent needs to cite and interpret results. Nothing an agent must know to call or report on it is missing.

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; the description goes beyond it by naming the exact section ids allowed in `sections`, stating that omitting it returns all, explaining the cap of 6 figures per section, and showing two literal example payloads. That clarifies the effect of each parameter rather than restating its type.

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+resource with scope: 'An overview of one place in a single call' with the nine figure sections enumerated. It also explicitly distinguishes itself from siblings ('For one figure use get_value; for a ranking use rank_places'), so the agent can route without opening other schemas.

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?

Gives concrete user-intent triggers ('give me an overview of Travis County', 'key statistics for Bavaria') and names the two alternatives with the condition that selects them (single figure -> get_value, ranking -> rank_places). Nothing is left to inference.

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

All Invokely official statistics 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