Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

find_regions

Read-only

Browse geographic regions; sort by provider/API count. Returns the 18 regions themselves. The collection also holds region x industry crossover pages (nordics-healthcare and 1,097 more); those are excluded unless you ask for them with type.

Input Schema

NameRequiredDescriptionDefault
qNoFree text matched against name and description, e.g. "payments".
pageNoPage number, 1-based (default 1).
sortNoOrder: name, api_count, provider_count or composite, e.g. "provider_count".
typeNoWhich record kind to list. `region` (default) is the dimension itself; `region-industry` is the crossover pages; `all` is both.region
limitNoResults per page, 1-100 (default 25).
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based (default 1). Use with `limit` to walk a long list."New value: +"Page number, 1-based (default 1)."
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / q / description
      Added value: +"Free text matched against name and description, e.g. \"payments\"."
    • addedInput schema / properties / sort / description
      Added value: +"Order: name, api_count, provider_count or composite, e.g. \"provider_count\"."
  3. Changed1 schema field changed
    • addedInput schema / properties / type
      Added value: +{
+  "default": "region",
+  "description": "Which record kind to list. `region` (default) is the dimension itself; `region-industry` is the crossover pages; `all` is both.",
+  "enum": [
+    "region",
+    "region-industry",
+    "all"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false. The description adds useful behavior beyond that: it discloses the exact result cardinality (18), that the underlying collection is larger, and the default exclusion rule — the kind of context that prevents an agent expecting crossover rows from being surprised.

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?

Three sentences, zero filler, purpose front-loaded in the first clause and the exclusion caveat placed last where it belongs. Every sentence earns its place.

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 no output schema, the description compensates by stating what a call returns (the 18 region records) and what it omits, and annotations cover the safety profile. Remaining gaps — pagination/total-count behaviour and output shape — are minor for a simple browse tool.

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 description coverage is 100%, so the schema already documents q, page, sort, type, limit and context. The description only reinforces the type default and the sort-by-count intent, adding marginal value over the structured fields — the baseline 3 applies.

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 and resource ("Browse geographic regions"), quantifies the scope ("Returns the 18 regions themselves"), and explicitly carves out what is NOT returned (region x industry crossover pages). This scoping makes it distinct from neighbours like find_industries, find_countries and the crossover-oriented get_region_leaders.

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 a clear conditional: crossover pages are "excluded unless you ask for them with type", which tells the agent how to widen its query. It stops short of naming sibling alternatives (get_region, find_countries) or when NOT to use this tool, so it is clear context rather than explicit routing.

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

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources