Skip to main content
Glama

Orcid

by io.github.pipeworx-io

Work

work
Read-onlyIdempotent

Single work record by put-code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orcid_idYes
put_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "orcid_id": "0000-0001-5109-3700",
+    "put_code": "12345678"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Single work record",
+  "type": "object"
+}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context beyond the put-code key, such as no mention of error conditions or auth requirements. This is acceptable given the strong annotation coverage but adds little value.

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?

The description is a single short sentence with no filler or repetition, making it very concise. However, it is a fragment lacking a verb, which slightly reduces clarity. Still, it is appropriately sized for a simple tool.

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

Completeness3/5

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

Given the tool's simplicity, the strong annotations, and the presence of an output schema, the description is minimally sufficient. It clearly indicates a single work record by put-code, but omits mention of the required orcid_id and any alternatives, leaving some gaps in usage context. It meets the minimum viable bar but could easily be enhanced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions put-code but does not explain orcid_id, or clarify the role of either parameter beyond their names. The schema has examples but no property descriptions, so the description adds only marginal meaning for put-code and none for orcid_id.

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 'Single work record by put-code' clearly identifies a resource (work record) and the key identifier (put-code). It implicitly distinguishes from sibling 'works' by signaling a single record, though it lacks an explicit verb like 'get' or 'retrieve'.

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 such as 'works' (plural) or other record types like 'education' or 'employment'. The description does not state any exclusions or context for selection.

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

All Orcid toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation2/5

The ORCID-specific tools (record, search, works, work) are reasonably distinct, but the set is dominated by unrelated Pipeworx/Polymarket tools, several of which overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions). ask_pipeworx_beta is explicitly described as currently identical to ask_pipeworx, creating genuine misselection risk.

Naming Consistency2/5

Naming conventions are mixed with no consistent pattern: nouns like 'record', 'work', 'works', and 'education' sit alongside snake_case verb phrases like 'search_within', 'validate_claim', and 'generate_llms_txt', plus proprietary 'ask_pipeworx' / 'pipeworx_feedback' names. While readable, the styles are inconsistent enough that an agent cannot predict tool names from the domain.

Tool Count2/5

37 tools is far too many for a server scoped as 'Orcid': only roughly 7 tools (record, works, work, education, employment, search, search_within) actually relate to ORCID. The remaining ~30 tools cover prediction markets, npm dependencies, AI visibility, and generic Pipeworx/Polymarket functionality, which is a severe scope mismatch.

Completeness3/5

For read-only ORCID access, the surface covers full records, works, education, employment, and registry search, with semantic search over fetched records as a useful addition. However, it lacks other common ORCID activity types (funding, peer review, distinctions), profile metadata beyond summaries, and any create/update/delete lifecycle operations, leaving notable gaps for a server claiming to serve ORCID data.

Resources