Get supported region codes for search filters and scope fields. No authentication required. Returns ISO 3166-1/2 codes (e.g. "US", "US-CA").
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable extra context: 'No authentication required' discloses an important access requirement, and 'Returns ISO 3166-1/2 codes' clarifies the output format, which is crucial since no output schema exists. This goes beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise—two short sentences that front-load the purpose and immediately provide key behavioral details (no auth, output format). Every word earns its place, with no redundant or irrelevant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with zero parameters, no output schema, and simple functionality, the description is complete. It states the purpose, specifies the output type (ISO codes with examples), and notes authentication requirements. Nothing essential is missing for an agent to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
This tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings. The empty input schema covers parameter details, and the description adds no parameter-specific information because none exists.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Get supported region codes for search filters and scope fields.' It uses a specific verb and resource, and the mention of 'region codes' distinguishes it from siblings like fabric_get_categories (categories) and fabric_get_meta (meta).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context by stating the codes are for 'search filters and scope fields,' implying when the tool is relevant. It does not explicitly mention alternatives or when not to use it, but the sibling tools cover different domains, so the context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
All 7 tools have clearly distinct purposes: identity creation, metadata retrieval, category/region discovery, session management, and two-step recovery. No overlap.
Every tool follows the 'fabric_<verb>_<noun>' pattern with consistent snake_case. Verbs are descriptive (create, get, login, recovery_start, recovery_complete) making the convention predictable.
7 tools cover essential identity lifecycle steps (creation, session, recovery) and discovery (categories, regions, meta). This is well-scoped for the domain without bloat.
Core creation and discovery tools exist, but missing configuration updates (e.g., webhook URL, recovery key setup) and identity deletion. The recovery flow is complete, but post-creation setup must be done manually or via other means.