Education
educationRead-onlyIdempotent
Education summary.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| orcid_id | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Orcid
Schema Changelog
Changes observed during successful MCP inspections.
Changed2 schema fields changed
- added
Input schema / examplesAdded value: +[ + { + "orcid_id": "0000-0001-5109-3700" + } +] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "description": "Education summary", + "type": "object" +}
- First observed
TDQS
D1.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only, idempotent, and non-destructive. The description 'Education summary' adds no behavioral context, such as what data is included, how it is filtered, or any limitations. It neither contradicts the annotations nor enriches them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely brief (two words) but fails to convey the essential purpose. It is under-specified rather than concise; every word is generic and doesn't earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one parameter and an output schema, the tool is simple, but the description is too sparse to understand the expected behavior or results. There is no indication of what an 'Education summary' contains or how it relates to an ORCID record.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema defines a single required 'orcid_id' string with no description, and the schema description coverage is 0%. The tool description does not explain what 'orcid_id' is or how it is used, leaving the parameter semantics entirely to the name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Education summary' is a noun phrase that restates the tool name without an action verb. It does not explicitly state what the tool does (e.g., retrieve or summarize education data) nor does it distinguish it from sibling tools like 'employment' or 'works'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided for when to use this tool. There are no mentions of alternatives, prerequisites, or exclusions. Sibling tools such as 'employment', 'works', and 'entity_profile' overlap in potential purpose, but the description offers no differentiator.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.