Skip to main content
Glama

crossref-mcp-server

Search Funders

crossref_search_funders
Read-only

Finds funders registered in the Crossref Funder Registry by name or funder DOI. Provide funder_doi for an exact single-funder lookup — the full DOI ("10.13039/100000001"), the bare registry ID ("100000001"), or either behind a doi: or https://doi.org/ prefix — or query for name-based search. Name-query results page with offset — the nextOffset enrichment carries the value for the following page, up to offset + rows = 100000. Set include_works to true to also return a page of the most recent works funded by the matched funder; that list pages two ways, in two orders. works_offset is the simple one: newest published first, capped ten times lower at works_offset + rows = 10000. works_cursor has no ceiling and reaches the whole funded-works list, newest registered first — ordered by the date each DOI was registered with Crossref, since Crossref does not walk a publication-date sort by cursor: pass works_cursor="*" on the first call, then chain the nextWorksCursor token from each response. The two cannot be combined, and a cursor walk always starts at the most recently registered work — it cannot resume from an offset. This list also counts works funded by the funder's registry descendants, which a crossref_search_works filter on {"funder": "10.13039/"} does not; a funder_doi lookup returns those descendants' registry IDs as descendants, and the funder's own ID OR'd with each of them in the funder filter ({"funder": ",funder:,…"}) counts the same scope with date, type, or other filters. Both it and that filter count the grant DOIs a funder registers as funded works. Returns funder name, registry ID, country, and alternate names, plus, on a funder_doi lookup, the Funder Registry's own work count for the ID and the same with its descendants (descendantWorksCount), both less grant records. The Funder Registry supersedes entries, and a deprecated one answers to the same names as its successor while carrying only a fraction of its works: such a record carries replacedBy with the superseding registry ID and the response carries a notice naming it. The replacement is never followed automatically — re-run with funder_doi set to that ID to get the current entry.

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": "crossref_search_funders"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoMaximum funders to return for name queries, or works when include_works is true (1–1000, default 10).
queryNoFunder name search query, e.g. "National Science Foundation" or "Wellcome Trust"
offsetNoZero-based offset into the name-query funder list. Pass the nextOffset value from the previous response to continue. Capped at offset + rows = 100000: a page that would pass it returns the funders that fit and says so in notice, and an offset at or past it is refused. Ignored when funder_doi is set, which resolves exactly one record.
funder_doiNoFunder DOI for exact lookup — the full DOI "10.13039/100000001" (NSF) or the bare registry ID "100000001". Supersedes query when provided.
works_cursorNoCursor token for deep paging of the funded-works list when include_works is true. Pass "*" to start the walk at the most recently registered work, then pass the nextWorksCursor value from each response. A walk runs by the date each DOI was registered with Crossref, newest first, not by publication date — Crossref does not walk a publication-date sort by cursor. Has no offset ceiling and cannot be combined with works_offset.
works_offsetNoZero-based offset into the funded-works list when include_works is true. Pass the nextWorksOffset value from the previous response to continue. Capped at works_offset + rows = 10000: a page that would pass it returns the works that fit and says so in notice, and a works_offset at or past it is refused; use works_cursor to read the whole list. Cannot be combined with works_cursor.
include_worksNoWhen true, also return a page of works funded by the matched funder. Requires an unambiguous funder — pass funder_doi when a name query matches more than one.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page whose offset + rows would pass one of the route offset ceilings, cut to the rows that fit (naming the rows requested and applied), a page that reaches one of those ceilings with records still unretrieved (naming the route to them), a returned funder that the Funder Registry has deprecated in favor of another entry, a funded-works row of type grant, which carries no title (naming crossref_get_work as the call that returns it), or a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered. Absent otherwise. A page needing more than one caveat carries them all in this one string.
fundersNoMatching funder records
nextOffsetNoValue to pass as offset on the next call for the following page of funders. Absent when this page ends the matches or reaches the 100000-record offset ceiling.
fundedWorksNoPage of works funded by the matched funder, newest first — by publication date on an offset page, by Crossref registration date on a works_cursor page. Only present when include_works is true.
funderCountNoNumber of funder records returned in this page
fundersTotalNoTotal funder records matching the query in Crossref
nextWorksCursorNoValue to pass as works_cursor on the next call for the following page of funded works. Present only on a page requested with works_cursor, and absent once the walk reaches the end of the works list.
nextWorksOffsetNoValue to pass as works_offset on the next call for the following page of funded works. Absent when this page ends the works list, reaches the 10000-record offset ceiling, or was requested with works_cursor.
fundedWorksTotalNoTotal of the matched funder's funded-works list when include_works is true: works funded by it or its registry descendants, grant records included — every grant DOI the funder and its descendants register counts as a funded work. A funder_doi lookup's descendantWorksCount is this total less those grant records. To count that scope without grants under other filters, OR the funder's ID with its descendants in a crossref_search_works funder filter with rows: 0, then subtract from totalResults the Grant count of facets {"type-name": "*"} or the totalResults of the same call with "type": "grant" added to the filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON, or with facet counts in a shape this server does not read. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset is at or past the 100000-record ceiling Crossref puts on offset + rows on funder name search, so no funder page starts there. `works_offset_too_large`: works_offset is at or past the 10000-record ceiling Crossref puts on works_offset + rows on a funded-works list, so no works page starts there. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget, or answered it to the single-attempt published-version lookup on a preprint. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON, or with facet counts in a shape this server does not read. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, did not answer before the 25 s request deadline (CROSSREF_TIMEOUT_MS when longer) that bounds every retry, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset is at or past the 100000-record ceiling Crossref puts on offset + rows on funder name search, so no funder page starts there. `works_offset_too_large`: works_offset is at or past the 10000-record ceiling Crossref puts on works_offset + rows on a funded-works list, so no works page starts there. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / fundedWorks / items / properties / title / description
      Previous value: -"Work title"New value: +"Work title. Absent on a grant record, which deposits none — crossref_get_work returns a grant's project titles."
    • changedOutput schema / properties / fundedWorksTotal / description
      Previous value: -"Total count of funded works for the matched funder, including works funded by its registry descendants, when include_works is true"New value: +"Total of the matched funder's funded-works list when include_works is true: works funded by it or its registry descendants, grant records included — every grant DOI the funder and its descendants register counts as a funded work. A funder_doi lookup's descendantWorksCount is this total less those grant records. To count that scope without grants under other filters, OR the funder's ID with its descendants in a crossref_search_works funder filter with rows: 0, then subtract from totalResults the Grant count of facets {\"type-name\": \"*\"} or the totalResults of the same call with \"type\": \"grant\" added to the filter."
    • addedOutput schema / properties / funders / items / properties / descendantWorksCount
      Added value: +{
      +  "description": "The Funder Registry record's work count across this funder and its registry descendants, less grant records: the funded-works list's total (fundedWorksTotal, with include_works) minus the grant records that list counts. Returned on a funder_doi lookup; name-query rows omit it.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / funders / items / properties / worksCount / description
      Previous value: -"The Funder Registry record's own work count for this ID, not counting the funder's registry descendants. It can differ from the total a crossref_search_works funder filter on the ID returns, which counts the works asserting it: for that exact figure, call crossref_search_works with filter {\"funder\": \"<id>\"} and rows: 0, and read totalResults. Returned on a funder_doi lookup; name-query rows omit it."New value: +"The Funder Registry record's own work count for this ID: the works a crossref_search_works funder filter on the ID matches, less the grant records among them, and not counting the funder's registry descendants (descendantWorksCount adds those). That filter counts every grant DOI the funder registers and this count does not. To count without grants under other filters, call crossref_search_works with filter {\"funder\": \"<id>\"} and rows: 0, then subtract from totalResults the Grant count of facets {\"type-name\": \"*\"} or the totalResults of the same call with \"type\": \"grant\" added to the filter. Returned on a funder_doi lookup; name-query rows omit it."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page whose offset + rows would pass one of the route offset ceilings, cut to the rows that fit (naming the rows requested and applied), a page that reaches one of those ceilings with records still unretrieved (naming the route to them), a returned funder that the Funder Registry has deprecated in favor of another entry, or a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered. Absent otherwise. A page needing more than one caveat carries them all in this one string."New value: +"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page whose offset + rows would pass one of the route offset ceilings, cut to the rows that fit (naming the rows requested and applied), a page that reaches one of those ceilings with records still unretrieved (naming the route to them), a returned funder that the Funder Registry has deprecated in favor of another entry, a funded-works row of type grant, which carries no title (naming crossref_get_work as the call that returns it), or a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered. Absent otherwise. A page needing more than one caveat carries them all in this one string."
  2. Changed3 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset is at or past the 100000-record ceiling Crossref puts on offset + rows on funder name search, so no funder page starts there. `works_offset_too_large`: works_offset is at or past the 10000-record ceiling Crossref puts on works_offset + rows on a funded-works list, so no works page starts there. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON, or with facet counts in a shape this server does not read. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset is at or past the 100000-record ceiling Crossref puts on offset + rows on funder name search, so no funder page starts there. `works_offset_too_large`: works_offset is at or past the 10000-record ceiling Crossref puts on works_offset + rows on a funded-works list, so no works page starts there. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / funders / items / properties / replaces / description
      Previous value: -"Registry IDs this funder supersedes. Present only when the funder has absorbed a deprecated entry; works registered against those IDs are not counted here."New value: +"Registry IDs this funder supersedes. Present only when the funder has absorbed a deprecated entry. A work asserting only one of these IDs is counted by neither the funded-works list nor a crossref_search_works funder filter on this ID; OR them with this ID in that filter to count the funder's whole history: {\"funder\": \"<id>,funder:<replaced>,…\"}."
    • changedOutput schema / properties / funders / items / properties / worksCount / description
      Previous value: -"Works asserting this registry ID alone — the total a crossref_search_works funder filter on this ID returns, not counting the funder's registry descendants. Returned on a funder_doi lookup; name-query rows omit it."New value: +"The Funder Registry record's own work count for this ID, not counting the funder's registry descendants. It can differ from the total a crossref_search_works funder filter on the ID returns, which counts the works asserting it: for that exact figure, call crossref_search_works with filter {\"funder\": \"<id>\"} and rows: 0, and read totalResults. Returned on a funder_doi lookup; name-query rows omit it."
  3. Changed10 schema fields changed
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based offset into the name-query funder list. Pass the nextOffset value from the previous response to continue. Ignored when funder_doi is set, which resolves exactly one record."New value: +"Zero-based offset into the name-query funder list. Pass the nextOffset value from the previous response to continue. Capped at offset + rows = 100000: a page that would pass it returns the funders that fit and says so in notice, and an offset at or past it is refused. Ignored when funder_doi is set, which resolves exactly one record."
    • changedInput schema / properties / rows / description
      Previous value: -"Maximum funders to return for name queries, or works when include_works is true (1–100 per call, default 10). A larger value, up to 1000, returns 100 and says so in notice; nextOffset and nextWorksOffset continue after the records returned."New value: +"Maximum funders to return for name queries, or works when include_works is true (1–1000, default 10)."
    • changedInput schema / properties / works_offset / description
      Previous value: -"Zero-based offset into the funded-works list when include_works is true. Pass the nextWorksOffset value from the previous response to continue. Capped at works_offset + rows = 10000; use works_cursor to read the whole list. Cannot be combined with works_cursor."New value: +"Zero-based offset into the funded-works list when include_works is true. Pass the nextWorksOffset value from the previous response to continue. Capped at works_offset + rows = 10000: a page that would pass it returns the works that fit and says so in notice, and a works_offset at or past it is refused; use works_cursor to read the whole list. Cannot be combined with works_cursor."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset + rows exceeds the 100000-record ceiling Crossref allows on funder name search. `works_offset_too_large`: works_offset + rows exceeds the 10000-record ceiling Crossref allows on a funded-works list. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset is at or past the 100000-record ceiling Crossref puts on offset + rows on funder name search, so no funder page starts there. `works_offset_too_large`: works_offset is at or past the 10000-record ceiling Crossref puts on works_offset + rows on a funded-works list, so no works page starts there. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / fundedWorksTotal / description
      Previous value: -"Total count of funded works for the matched funder, when include_works is true"New value: +"Total count of funded works for the matched funder, including works funded by its registry descendants, when include_works is true"
    • addedOutput schema / properties / funders / items / properties / descendants
      Added value: +{
      +  "description": "Registry IDs of every funder below this one in the Funder Registry hierarchy, at every depth, bare as Crossref lists them (\"100000054\"). Present on a funder_doi lookup of a funder that has any; name-query rows never carry it. The funded-works list counts their works; to count that scope with filters, OR this funder's ID and each of these in a crossref_search_works funder filter: {\"funder\": \"<id>,funder:<descendant>,…\"}.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / funders / items / properties / worksCount / description
      Previous value: -"Number of works associated with this funder in Crossref"New value: +"Works asserting this registry ID alone — the total a crossref_search_works funder filter on this ID returns, not counting the funder's registry descendants. Returned on a funder_doi lookup; name-query rows omit it."
    • changedOutput schema / properties / nextOffset / description
      Previous value: -"Value to pass as offset on the next call for the following page of funders. Absent when this page ends the matches or the next page would breach the 100000-record offset ceiling."New value: +"Value to pass as offset on the next call for the following page of funders. Absent when this page ends the matches or reaches the 100000-record offset ceiling."
    • changedOutput schema / properties / nextWorksOffset / description
      Previous value: -"Value to pass as works_offset on the next call for the following page of funded works. Absent when this page ends the works list, the next page would breach the 10000-record offset ceiling, or the page was requested with works_cursor."New value: +"Value to pass as works_offset on the next call for the following page of funded works. Absent when this page ends the works list, reaches the 10000-record offset ceiling, or was requested with works_cursor."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page that stops at one of the route offset ceilings with records still unretrieved (naming the offset and smaller rows that reach the last records below the ceiling, when any remain), a returned funder that the Funder Registry has deprecated in favor of another entry, a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered, or a rows value above its per-call cap, naming the value requested and the cap applied. Absent otherwise. A page needing more than one caveat carries them all in this one string."New value: +"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page whose offset + rows would pass one of the route offset ceilings, cut to the rows that fit (naming the rows requested and applied), a page that reaches one of those ceilings with records still unretrieved (naming the route to them), a returned funder that the Funder Registry has deprecated in favor of another entry, or a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered. Absent otherwise. A page needing more than one caveat carries them all in this one string."
  4. Changed3 schema fields changed
    • changedInput schema / properties / rows / description
      Previous value: -"Maximum funders to return for name queries, or works when include_works is true (1–100, default 10)"New value: +"Maximum funders to return for name queries, or works when include_works is true (1–100 per call, default 10). A larger value, up to 1000, returns 100 and says so in notice; nextOffset and nextWorksOffset continue after the records returned."
    • changedInput schema / properties / rows / maximum
      Previous value: -100New value: +1000
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page that stops at one of the route offset ceilings with records still unretrieved, a returned funder that the Funder Registry has deprecated in favor of another entry, or a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered. Absent otherwise. A page needing more than one caveat carries them all in this one string."New value: +"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page that stops at one of the route offset ceilings with records still unretrieved (naming the offset and smaller rows that reach the last records below the ceiling, when any remain), a returned funder that the Funder Registry has deprecated in favor of another entry, a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered, or a rows value above its per-call cap, naming the value requested and the cap applied. Absent otherwise. A page needing more than one caveat carries them all in this one string."
  5. Changed9 schema fields changed
    • addedInput schema / properties / funder_doi / anyOf
      Added value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Funder registry ID or funder DOI, e.g. \"100000001\"",
      +    "pattern": "^(?:(?:https?:\\/\\/(?:dx\\.)?doi\\.org\\/|doi:)?10\\.13039\\/)?\\d+$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / funder_doi / pattern
      Removed value: -"^(?:(?:https?:\\/\\/(?:dx\\.)?doi\\.org\\/|doi:)?10\\.13039\\/)?\\d+$"
    • removedInput schema / properties / funder_doi / type
      Removed value: -"string"
    • changedInput schema / properties / rows / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / works_cursor / description
      Previous value: -"Cursor token for deep paging of the funded-works list when include_works is true. Pass \"*\" to start the walk at the newest work, then pass the nextWorksCursor value from each response. Has no offset ceiling and cannot be combined with works_offset. Each token runs about 1500 characters and is returned on both result surfaces, a fixed cost per page — raise rows to spread it across more works on a long walk."New value: +"Cursor token for deep paging of the funded-works list when include_works is true. Pass \"*\" to start the walk at the most recently registered work, then pass the nextWorksCursor value from each response. A walk runs by the date each DOI was registered with Crossref, newest first, not by publication date — Crossref does not walk a publication-date sort by cursor. Has no offset ceiling and cannot be combined with works_offset."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset + rows exceeds the 100000-record ceiling Crossref allows on funder name search. `works_offset_too_large`: works_offset + rows exceeds the 10000-record ceiling Crossref allows on a funded-works list. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: Crossref answered HTTP 429 and the limit did not clear inside the retry budget. `upstream_unavailable`: Crossref was unreachable, returned a 5xx status, or served an HTML error page instead of JSON. `malformed_response`: Crossref returned HTTP 200 with a body that is not valid JSON. `request_timeout`: Crossref did not respond within CROSSREF_TIMEOUT_MS, or answered HTTP 408/504. `invalid_cursor`: Crossref did not recognize the cursor token (HTTP 404 cursor-invalid). `invalid_parameter`: Crossref rejected a parameter value (a filter value of the wrong type or form), or answered HTTP 400 with a body that did not parse. `funder_not_found`: Funder DOI lookup returned 404 — funder is not in the Crossref Funder Registry. `ambiguous_funder`: include_works is true but the name query matched more than one funder, making the target ambiguous. `offset_too_large`: offset + rows exceeds the 100000-record ceiling Crossref allows on funder name search. `works_offset_too_large`: works_offset + rows exceeds the 10000-record ceiling Crossref allows on a funded-works list. `works_cursor_offset_conflict`: include_works is true and works_cursor was supplied alongside a works_offset above zero. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "rate_limited",
      -  "upstream_unavailable",
      -  "malformed_response",
      -  "request_timeout",
      -  "funder_not_found",
      -  "ambiguous_funder",
      -  "offset_too_large",
      -  "works_offset_too_large",
      -  "works_cursor_offset_conflict"
      -]New value: +[
      +  "rate_limited",
      +  "upstream_unavailable",
      +  "malformed_response",
      +  "request_timeout",
      +  "invalid_cursor",
      +  "invalid_parameter",
      +  "funder_not_found",
      +  "ambiguous_funder",
      +  "offset_too_large",
      +  "works_offset_too_large",
      +  "works_cursor_offset_conflict"
      +]
    • changedOutput schema / properties / fundedWorks / description
      Previous value: -"Page of works funded by the matched funder, ordered by publication date (newest first). Only present when include_works is true."New value: +"Page of works funded by the matched funder, newest first — by publication date on an offset page, by Crossref registration date on a works_cursor page. Only present when include_works is true."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance on a page that needs a caveat: a query nothing matched, an offset past the end of a list that did match, a page that stops at one of the route offset ceilings with records still unretrieved, or a returned funder that the Funder Registry has deprecated in favor of another entry. Absent otherwise. A page needing more than one caveat carries them all in this one string."New value: +"Guidance on a page that needs a caveat: a query nothing matched, an offset or works_offset past the end of a list that did match, a page that stops at one of the route offset ceilings with records still unretrieved, a returned funder that the Funder Registry has deprecated in favor of another entry, or a query or funder_doi supplied blank with nothing else to search by, so the page lists every funder unfiltered. Absent otherwise. A page needing more than one caveat carries them all in this one string."
  6. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the interesting behavior — and it does: pagination ceilings (offset + rows = 100000, works capped at 10000), the fact that a cursor walk cannot resume from an offset, that cursor ordering is by DOI registration date not publication date, that descendants and grant DOIs are counted, and that deprecated registry entries carry replacedBy and are never followed automatically. That is exactly the kind of beyond-annotation context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core routing information is front-loaded and nothing is actively misleading, but the description is a dense run-on passage that re-states several schema-documented limits (the 100000 and 10000 ceilings appear in both). Given a 7-parameter tool it is defensible in length, yet breaking it into short labeled sentences would have made the offset/cursor distinction far easier to parse.

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?

The tool has an output schema, yet the description still summarizes the return shape (name, registry ID, country, alternate names, descendantWorksCount, notice, replacedBy) which is useful for deciding whether a response needs follow-up. Combined with the pagination and deprecation guidance, nothing an agent needs in order to call it correctly appears to be 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 earns extra by adding cross-parameter semantics the schema cannot express — funder_doi prefix handling (doi:/https://doi.org/), the mutual exclusion of works_cursor and works_offset, chaining nextOffset/nextWorksCursor/nextWorksOffset, and the requirement that include_works needs an unambiguous funder. Some of this duplicates the schema text, which keeps it from a 5.

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?

The opening sentence gives a specific verb and resource — finds funders in the Crossref Funder Registry — and immediately names the two lookup modes (name vs funder DOI). This is clearly distinguishable from sibling tools like crossref_search_works or crossref_search_journals.

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?

The description explicitly routes between modes: funder_doi for exact single-funder lookup, query for name search, and it spells out the works_offset vs works_cursor tradeoff (ceiling vs no ceiling, two different sort orders, cannot be combined). It also contrasts scope with a crossref_search_works funder filter. It stops short of saying outright when to prefer this tool over crossref_search_works for other purposes.

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.