Loading ToolBench
Search and retrieve researcher profiles, works, affiliations, funding, and peer review records from the ORCID registry via MCP. STDIO or Streamable HTTP.
Six tools with strong naming (verb_noun pattern), comprehensive descriptions (150-250 chars each), and complete JSON Schema input definitions. All parameters are typed and described. Output schemas are not explicitly documented in the source code provided, which is a notable gap. Tool descriptions are LLM-optimized and include context about data reliability and use cases. Error handling is implicit (READ_ONLY risk classification) but not explicitly documented in tool definitions. No security concerns detected (read-only operations, no credential parameters). Composition is clean, each tool has a single responsibility and clear chaining via orcid_id parameter.
Fetch affiliation records for an ORCID researcher. The `types` parameter controls which affiliation sections to return: employment, education, invited-positions, distinctions, memberships, qualifications, services, or all. Default is employment and education. Returns organization names, disambiguated organization identifiers (ROR/GRID/Ringgold), departments, roles, and date ranges. Affiliation data is self-reported; absence does not mean no affiliation.
Fetch funding records for an ORCID researcher: grants, contracts, awards, and salary awards. Returns funder names, funder organization identifiers, grant numbers, and funding periods. Funding data is entirely self-reported — most researchers do not enter funding even when they have grants. Absence of funding records does not imply absence of funding. When records exist they are high-value for grant tracking and funder analysis.
Fetch peer review activity for an ORCID researcher: convening organizations (journals and publishers), reviewer role (reviewer, editor, chair, etc.), review type, completion dates, and ISSN-keyed group identifiers. Use to assess editorial activity, journal affiliations, and the scope of a researcher's peer review contributions. Peer review records are self-reported or imported by participating publishers — coverage varies by researcher.
Fetch a researcher's public profile from ORCID: name, biography, keywords, researcher URLs, and external identifiers such as Scopus Author ID, ResearcherID, and Loop profile. This is the entry point for building a researcher dossier. Pass a bare ORCID iD (0000-0001-2345-6789) or a full URI (https://orcid.org/0000-0001-2345-6789). The profile contains only publicly visible data — researchers control visibility per field.
Output schemas not documented in tool definitions. LLMs cannot plan downstream operations or extract specific fields without knowing the response structure.
Error handling guidance missing from tool descriptions. Tools should document what errors are possible and how to recover (e.g., 'If ORCID not found, try search_orcid first').
orcid_get_work_detail accepts 1 - 100 put-codes but does not document per-item error handling. Description states 'per-record errors are surfaced as error entries' but the response schema is not shown, making it unclear how LLMs should parse partial failures.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2026-07-28+ | v2 |
List research resources associated with an ORCID researcher — compute allocations, equipment access, lab facilities, data resources, and clinical study registrations. This is a newer ORCID section; most researchers have no entries. Returns the resource title, hosting organization, external identifiers (often a URI to the allocation portal), and access period. Most entries are deposited by resource-allocation systems (e.g. ACCESS, XSEDE) rather than researchers themselves.
Fetch full detail records for 1–100 works by their put-codes in a single request. Put-codes are returned by orcid_get_works in the putCode field of each work entry. Returns the abstract (short-description), all contributors with CRediT roles, the complete external ID list (DOI, PMID, arXiv, ISBN, etc.), citation metadata (BibTeX or other formats when provided), journal title, and URL for each work. Per-record errors (not-found or inaccessible put-codes) are surfaced as error entries rather than failing the whole call.
ORCID identifier parameter accepts both bare format (0000-0001-2345-6789) and full URI (https://orcid.org/...). Description documents this, but no validation guidance is provided. LLMs may pass malformed identifiers.
No pagination parameters (limit, offset, page) documented for tools that may return large result sets (e.g., orcid_get_work_detail with 100 put-codes). Response structure and result limits are not specified.