Skip to main content
Glama

inaturalist-mcp-server

Inaturalist Get Histogram

inaturalist_get_histogram
Read-only

Build a phenology histogram for a taxon in an area — which months, weeks, or years it is recorded in. The default month_of_year interval answers "when does this bloom or appear here" in twelve buckets; absolute intervals (year, month, week, day, hour) bucket real dates and disclose their window start. An area is given in exactly one form: place_id, the lat/lng/radius triple in kilometres, or a four-corner bounding box. Omit taxon_id to chart every taxon in the area. Narrow to one life stage or reproductive state with an annotation pair (term_id and term_value_id, e.g. Life Stage = Larva, or Flowers and Fruits = Flowers), or to broad groups with iconic_taxa. Defaults to research-grade, wild-only records and echoes those defaults back.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inaturalist_get_histogram"
  }
}

Input Schema

NameRequiredDescriptionDefault
d1NoEarliest observation date, YYYY-MM-DD. Inclusive. Must be on or before d2. For absolute observed-date intervals, a missing d1 is derived from d2 or today UTC and disclosed as window_start. Wide ranges can exceed the 25000-bucket cap; continuation names d1, or created_d1 for upload-date bucketing.
d2NoLatest observation date, YYYY-MM-DD. Inclusive.
latNoLatitude of the search centre, in decimal degrees. Requires lng and radius.
lngNoLongitude of the search centre, in decimal degrees. Requires lat and radius.
nelatNoNorth-east corner latitude of the bounding box, at or north of swlat. All four corners or none.
nelngNoNorth-east corner longitude of the bounding box. All four corners or none. West of swlng is accepted: it describes a box crossing the antimeridian.
swlatNoSouth-west corner latitude of the bounding box. All four corners or none.
swlngNoSouth-west corner longitude of the bounding box. All four corners or none.
radiusNoSearch radius around lat/lng, in KILOMETRES, greater than 0. Requires lat and lng. Ceiling: 20040; oversized values are clamped with notice.
captiveNoTrue returns captive and cultivated records only — zoo animals, garden plantings; false returns wild records only. Defaults to false. Captive records are graded casual, so pair true with "casual" in quality_grade.
term_idNoAnnotation attribute ids, from inaturalist_list_reference topic controlled_terms — e.g. 1 for Life Stage. Multiple ids match any one annotation, not all annotations; arrays are membership sets, not positional pairs.
user_idNoRestrict to one observer, by numeric user id from inaturalist_resolve_name type user. Mutually exclusive with user_login.
intervalNoBucketing. month_of_year and week_of_year fold every year together into a seasonal curve. Absolute intervals default the selected date family's missing lower bound from its upper bound, otherwise today UTC: year/month subtract 100 calendar years, week 10 years, day one year, hour seven days. The start is disclosed; no upper bound is added. At most 25000 buckets are returned, oldest first, with continuation guidance when cut.month_of_year
place_idNoNumeric iNaturalist place id from inaturalist_find_places. Mutually exclusive with the lat/lng/radius triple and the bounding box.
taxon_idNoRestrict to this taxon and its descendants. Omit to chart every taxon in the area. Resolve a name to an id with inaturalist_resolve_name.
created_d1NoEarliest upload date, YYYY-MM-DD. Inclusive. Must be on or before created_d2.
created_d2NoLatest upload date, YYYY-MM-DD. Inclusive.
date_fieldNoWhich date to bucket by: when the organism was observed, or when the record was uploaded.observed
project_idNoRestrict to observations in one project, by numeric project id from inaturalist_resolve_name type project.
user_loginNoRestrict to one observer, by login — the login on an inaturalist_resolve_name user candidate, a leaderboard entry, or an observation’s observer. Mutually exclusive with user_id.
iconic_taxaNoBroad organism groups, by their scientific iconic-taxon name — Aves, not "Birds"; inaturalist_list_reference topic iconic_taxa lists them.
quality_gradeNoIdentification confidence tiers to include, normalized to unique values in first-appearance order. Defaults to research-grade only; adding "needs_id" roughly doubles the corpus and lowers identification confidence.
term_value_idNoAnnotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id. Multiple ids match any one annotation with an attribute in term_id and a value in this set, not both annotations.

Output Schema

NameRequiredDescriptionDefault
capNoThe bucket cap that was applied.
errorNoPresent when the call failed. Absent on success.
shownNoHow many buckets this response carries.
totalNoObservations in the upstream histogram window: sum of every returned bucket count, including buckets past the cap; not an all-time taxon count.
noticeNoGenerated window start, filter guidance, and continuation when buckets are cut.
bucketsNoEvery bucket upstream returned, in order, including the zero ones — up to 25000, the first in upstream key order. See the truncated/shown/cap enrichment when more exist.
intervalNoThe bucketing that was applied.
truncatedNoTrue when upstream returned more than 25000 buckets.
applied_filtersNoEffective cohort defaults, bucketed date family, and absolute window start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / captive / description
      Previous value: -"True returns captive and cultivated records only — zoo animals, garden plantings; false returns wild records only. Defaults to false."New value: +"True returns captive and cultivated records only — zoo animals, garden plantings; false returns wild records only. Defaults to false. Captive records are graded casual, so pair true with \"casual\" in quality_grade."
    • changedInput schema / properties / iconic_taxa / description
      Previous value: -"Broad organism groups, by their scientific iconic-taxon name. A common-name value such as \"Birds\" matches nothing upstream, so only the listed values are accepted."New value: +"Broad organism groups, by their scientific iconic-taxon name — Aves, not \"Birds\"; inaturalist_list_reference topic iconic_taxa lists them."
    • changedInput schema / properties / place_id / description
      Previous value: -"Numeric iNaturalist place id from inaturalist_find_places. Mutually exclusive with the lat/lng/radius triple and the bounding box. A non-numeric value answers HTTP 500 upstream."New value: +"Numeric iNaturalist place id from inaturalist_find_places. Mutually exclusive with the lat/lng/radius triple and the bounding box."
    • changedInput schema / properties / term_value_id / description
      Previous value: -"Annotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id; sent alone it is ignored upstream and the unfiltered corpus comes back. Multiple ids match any one annotation with an attribute in term_id and a value in this set, not both annotations."New value: +"Annotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id. Multiple ids match any one annotation with an attribute in term_id and a value in this set, not both annotations."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `conflicting_observer`: user_id and user_login were both supplied. `unknown_user`: iNaturalist answered 422 because the user_id or user_login names no observer. `unknown_project_id`: iNaturalist answered 422 because the project_id does not exist. `unknown_place_id`: iNaturalist answered 422 because place_id does not exist. `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2, or created_d1 is after created_d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `conflicting_observer`: user_id and user_login were both supplied. `unknown_user`: iNaturalist answered 422 because the user_id or user_login names no observer. `unknown_project_id`: iNaturalist answered 422 because the project_id does not exist. `unknown_place_id`: iNaturalist answered 422 because place_id does not exist. `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2, or created_d1 is after created_d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. `rate_budget_exhausted`: This server has spent its daily iNaturalist request budget for the current UTC day. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "conflicting_observer",
      -  "unknown_user",
      -  "unknown_project_id",
      -  "unknown_place_id",
      -  "invalid_geography",
      -  "inverted_date_range",
      -  "unpaired_annotation_value",
      -  "unknown_taxon_id"
      -]New value: +[
      +  "conflicting_observer",
      +  "unknown_user",
      +  "unknown_project_id",
      +  "unknown_place_id",
      +  "invalid_geography",
      +  "inverted_date_range",
      +  "unpaired_annotation_value",
      +  "unknown_taxon_id",
      +  "rate_budget_exhausted"
      +]
  2. Changed8 schema fields changed
    • changedInput schema / properties / d1 / description
      Previous value: -"Earliest observation date, YYYY-MM-DD. Inclusive. Must be on or before d2. With interval set to day or hour, a wide range can exceed the 800-bucket cap — narrow d1/d2 to reach buckets past it."New value: +"Earliest observation date, YYYY-MM-DD. Inclusive. Must be on or before d2. For absolute observed-date intervals, a missing d1 is derived from d2 or today UTC and disclosed as window_start. Wide ranges can exceed the 25000-bucket cap; continuation names d1, or created_d1 for upload-date bucketing."
    • changedInput schema / properties / interval / description
      Previous value: -"Bucketing. month_of_year and week_of_year fold every year together into a seasonal curve; the rest bucket absolute dates. day and hour over a wide date range can generate thousands of buckets — the response is capped at 800, kept from the start of the range; narrow d1/d2 or use a coarser interval to see the rest."New value: +"Bucketing. month_of_year and week_of_year fold every year together into a seasonal curve. Absolute intervals default the selected date family's missing lower bound from its upper bound, otherwise today UTC: year/month subtract 100 calendar years, week 10 years, day one year, hour seven days. The start is disclosed; no upper bound is added. At most 25000 buckets are returned, oldest first, with continuation guidance when cut."
    • changedOutput schema / properties / applied_filters / description
      Previous value: -"The server-applied defaults that determine what this answer means."New value: +"Effective cohort defaults, bucketed date family, and absolute window start."
    • addedOutput schema / properties / applied_filters / properties / window_start
      Added value: +{
      +  "description": "Inclusive lower bound on the bucketed date for absolute intervals; absent for seasonal intervals.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / buckets / description
      Previous value: -"Every bucket upstream returned, in order, including the zero ones — up to 800, the first in upstream key order. See the truncated/shown/cap enrichment when more exist."New value: +"Every bucket upstream returned, in order, including the zero ones — up to 25000, the first in upstream key order. See the truncated/shown/cap enrichment when more exist."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when every bucket came back zero, or when the cap was reached."New value: +"Generated window start, filter guidance, and continuation when buckets are cut."
    • changedOutput schema / properties / total / description
      Previous value: -"Sum of every bucket count upstream returned, including buckets past the cap that are not in the buckets array."New value: +"Observations in the upstream histogram window: sum of every returned bucket count, including buckets past the cap; not an all-time taxon count."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when upstream returned more than 800 buckets."New value: +"True when upstream returned more than 25000 buckets."
  3. Changed9 schema fields changed
    • addedInput schema / properties / project_id
      Added value: +{
      +  "description": "Restrict to observations in one project, by numeric project id from inaturalist_resolve_name type project.",
      +  "maximum": 2147483647,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius around lat/lng, in KILOMETRES, greater than 0. Requires lat and lng. The upstream publishes no bound; 500 is a verified ceiling this server imposes."New value: +"Search radius around lat/lng, in KILOMETRES, greater than 0. Requires lat and lng. Ceiling: 20040; oversized values are clamped with notice."
    • removedInput schema / properties / radius / maximum
      Removed value: -500
    • changedInput schema / properties / term_id / description
      Previous value: -"Annotation attribute ids, from inaturalist_list_reference topic controlled_terms — e.g. 1 for Life Stage."New value: +"Annotation attribute ids, from inaturalist_list_reference topic controlled_terms — e.g. 1 for Life Stage. Multiple ids match any one annotation, not all annotations; arrays are membership sets, not positional pairs."
    • changedInput schema / properties / term_value_id / description
      Previous value: -"Annotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id; sent alone it is ignored upstream and the unfiltered corpus comes back."New value: +"Annotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id; sent alone it is ignored upstream and the unfiltered corpus comes back. Multiple ids match any one annotation with an attribute in term_id and a value in this set, not both annotations."
    • addedInput schema / properties / user_id
      Added value: +{
      +  "description": "Restrict to one observer, by numeric user id from inaturalist_resolve_name type user. Mutually exclusive with user_login.",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / user_login
      Added value: +{
      +  "description": "Restrict to one observer, by login — the login on an inaturalist_resolve_name user candidate, a leaderboard entry, or an observation’s observer. Mutually exclusive with user_id.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `unknown_place_id`: iNaturalist answered 422 because place_id does not exist. `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2, or created_d1 is after created_d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `conflicting_observer`: user_id and user_login were both supplied. `unknown_user`: iNaturalist answered 422 because the user_id or user_login names no observer. `unknown_project_id`: iNaturalist answered 422 because the project_id does not exist. `unknown_place_id`: iNaturalist answered 422 because place_id does not exist. `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2, or created_d1 is after created_d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "unknown_place_id",
      -  "invalid_geography",
      -  "inverted_date_range",
      -  "unpaired_annotation_value",
      -  "unknown_taxon_id"
      -]New value: +[
      +  "conflicting_observer",
      +  "unknown_user",
      +  "unknown_project_id",
      +  "unknown_place_id",
      +  "invalid_geography",
      +  "inverted_date_range",
      +  "unpaired_annotation_value",
      +  "unknown_taxon_id"
      +]
  4. Changed7 schema fields changed
    • changedInput schema / properties / captive / description
      Previous value: -"Whether to include captive and cultivated records — zoo animals, garden plantings. Defaults to wild organisms only."New value: +"True returns captive and cultivated records only — zoo animals, garden plantings; false returns wild records only. Defaults to false."
    • addedInput schema / properties / created_d1
      Added value: +{
      +  "description": "Earliest upload date, YYYY-MM-DD. Inclusive. Must be on or before created_d2.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / created_d2
      Added value: +{
      +  "description": "Latest upload date, YYYY-MM-DD. Inclusive.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / quality_grade / description
      Previous value: -"Identification confidence tiers to include. Defaults to research-grade only; adding \"needs_id\" roughly doubles the corpus and lowers identification confidence."New value: +"Identification confidence tiers to include, normalized to unique values in first-appearance order. Defaults to research-grade only; adding \"needs_id\" roughly doubles the corpus and lowers identification confidence."
    • changedOutput schema / properties / applied_filters / properties / captive / description
      Previous value: -"Whether captive and cultivated records were included."New value: +"Captive-only when true, wild-only when false."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `unknown_place_id`: iNaturalist answered 422 because place_id does not exist. `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2, or created_d1 is after created_d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_geography",
      -  "inverted_date_range",
      -  "unpaired_annotation_value",
      -  "unknown_taxon_id"
      -]New value: +[
      +  "unknown_place_id",
      +  "invalid_geography",
      +  "inverted_date_range",
      +  "unpaired_annotation_value",
      +  "unknown_taxon_id"
      +]
  5. Changed5 schema fields changed
    • addedInput schema / properties / iconic_taxa
      Added value: +{
      +  "description": "Broad organism groups, by their scientific iconic-taxon name. A common-name value such as \"Birds\" matches nothing upstream, so only the listed values are accepted.",
      +  "items": {
      +    "enum": [
      +      "Actinopterygii",
      +      "Amphibia",
      +      "Animalia",
      +      "Arachnida",
      +      "Aves",
      +      "Chromista",
      +      "Fungi",
      +      "Insecta",
      +      "Mammalia",
      +      "Mollusca",
      +      "Plantae",
      +      "Protozoa",
      +      "Reptilia",
      +      "unknown"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / term_id
      Added value: +{
      +  "description": "Annotation attribute ids, from inaturalist_list_reference topic controlled_terms — e.g. 1 for Life Stage.",
      +  "items": {
      +    "maximum": 9007199254740991,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / term_value_id
      Added value: +{
      +  "description": "Annotation value ids, from the same attribute listing — e.g. 6 for Larva. Requires term_id; sent alone it is ignored upstream and the unfiltered corpus comes back.",
      +  "items": {
      +    "maximum": 9007199254740991,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2. `unpaired_annotation_value`: term_value_id was supplied without term_id. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_geography",
      -  "inverted_date_range",
      -  "unknown_taxon_id"
      -]New value: +[
      +  "invalid_geography",
      +  "inverted_date_range",
      +  "unpaired_annotation_value",
      +  "unknown_taxon_id"
      +]
  6. Changed7 schema fields changed
    • changedInput schema / properties / d1 / description
      Previous value: -"Earliest observation date, YYYY-MM-DD. Inclusive. With interval set to day or hour, a wide range can exceed the 800-bucket cap — narrow d1/d2 to reach buckets past it."New value: +"Earliest observation date, YYYY-MM-DD. Inclusive. Must be on or before d2. With interval set to day or hour, a wide range can exceed the 800-bucket cap — narrow d1/d2 to reach buckets past it."
    • changedInput schema / properties / nelat / description
      Previous value: -"North-east corner latitude of the bounding box. All four corners or none."New value: +"North-east corner latitude of the bounding box, at or north of swlat. All four corners or none."
    • changedInput schema / properties / nelng / description
      Previous value: -"North-east corner longitude of the bounding box. All four corners or none."New value: +"North-east corner longitude of the bounding box. All four corners or none. West of swlng is accepted: it describes a box crossing the antimeridian."
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius around lat/lng, in KILOMETRES. Requires lat and lng. The upstream publishes no bound; 500 is a verified ceiling this server imposes."New value: +"Search radius around lat/lng, in KILOMETRES, greater than 0. Requires lat and lng. The upstream publishes no bound; 500 is a verified ceiling this server imposes."
    • removedInput schema / properties / radius / minimum
      Removed value: -0
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_geography`: An area was given partially or in two forms at once. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_geography`: An area was given partially, in two forms at once, with a radius of 0 or less, or with nelat south of swlat. `inverted_date_range`: d1 is after d2. `unknown_taxon_id`: iNaturalist answered 422 because the taxon_id does not exist. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_geography",
      -  "unknown_taxon_id"
      -]New value: +[
      +  "invalid_geography",
      +  "inverted_date_range",
      +  "unknown_taxon_id"
      +]
  7. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior the agent could not infer: research-grade and wild-only defaults are echoed back, absolute intervals disclose their window start, and results are capped with continuation guidance. These are exactly the operational details that affect interpretation of results.

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?

Purpose is front-loaded in the first sentence and the rest is organized by concern (interval, area, filters, defaults). The sentences are long and clause-dense, with some overlap against schema text, but no filler sentences.

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 23-parameter, zero-required tool with an output schema, the description covers the critical decision points: default interval semantics, the exactly-one area form rule, the option to omit taxon, filter narrowing, and the bucket cap with continuation. Nothing essential to correct invocation is missing.

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 carries the parameter semantics; the description largely restates them (three mutually exclusive area forms, the term_id/term_value_id pair, twelve month_of_year buckets). It adds little syntax or format detail beyond the schema, so 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 — 'Build a phenology histogram for a taxon in an area' — and immediately clarifies what the output means ('which months, weeks, or years it is recorded in'). This distinguishes it from counting/searching siblings like inaturalist_get_species_counts or inaturalist_search_observations without needing their schemas.

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 clear situational guidance: default month_of_year answers 'when does this bloom or appear here', omit taxon_id to chart everything in the area, and use an annotation pair or iconic_taxa to narrow. It does not explicitly name a sibling alternative or state when to prefer a different tool, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.