eBird MCP Server

get_region_info

Retrieve detailed information about eBird regions including boundaries, hierarchical structure, and formatted names to support bird observation data analysis.

Instructions

Get information about a region including name, bounds, and parent hierarchy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region_code": "<region_code>"
    },
    "name": "get_region_info"
  }
}

Input Schema

Name	Required	Description	Default
`region_code`	Yes	Country, subnational1, subnational2, or location code
`region_name_format`	No	Name format	full
`delim`	No	Delimiter for name elements	,

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states what information is returned but doesn't disclose behavioral traits such as rate limits, authentication needs, error conditions, or response format. For a read operation with no annotations, this leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence that front-loads the purpose and lists key information returned. Every word earns its place with no redundancy or unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain return values, error handling, or behavioral constraints. For a tool with 3 parameters and complex sibling context, more detail is needed to ensure the agent can use it correctly.

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 fully documents parameters. The description doesn't add meaning beyond what the schema provides, such as explaining region_code hierarchies or practical use of name formats. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the verb ('Get') and resource ('region information'), specifying what information is included (name, bounds, parent hierarchy). It distinguishes from most siblings that focus on observations, checklists, or hotspots rather than region metadata, though it doesn't explicitly differentiate from get_sub_regions or get_adjacent_regions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like get_sub_regions or get_adjacent_regions. The description implies usage for region metadata but doesn't specify prerequisites, exclusions, or comparative contexts with sibling tools.

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