Skip to main content
Glama

Get a Workday doc page

get_workday_doc
Read-onlyIdempotent

Retrieve the full markdown content of a Workday documentation page using its ID or URL. Returns markdown and canonical link, even if body fetch fails.

Instructions

Fetch the full markdown for one Workday documentation page.

Accepts EITHER a doc_id (from search_workday_docs) OR a developer.workday.com "/wcp_docs/.html" link. Always returns the canonical html_url so you can cite/link the page even if the body can't be fetched.

Args:

  • doc_id (string): a doc ID from search_workday_docs

  • html_url (string): alternatively, a developer.workday.com/wcp_docs/.html link

Returns: { doc_id, html_url, truncated, markdown, error? }

  • markdown: the page body (string), or null if the body fetch failed (see error)

  • truncated: true if the body exceeded 60000 chars and was cut

  • error: present only when the body could not be fetched (html_url is still valid to link)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idNoDoc ID from search_workday_docs
html_urlNoA developer.workday.com/wcp_docs/<id>.html link

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYes
html_urlYes
truncatedYes
markdownYes
errorNo
Behavior4/5

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

Annotations (readOnlyHint, idempotentHint, etc.) already indicate safety, but the description adds valuable behavioral details: truncation at 60k chars, error field only present on body fetch failure, and that html_url is always returned. This goes beyond annotations and provides a clear mental model of tool operation.

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

Conciseness5/5

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

The description is remarkably concise: a single-sentence purpose followed by two short paragraphs covering usage and return format. Every sentence adds value, with no redundancy or filler. The structure is front-loaded and easy to scan.

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?

Given the tool's simplicity (two optional parameters, no nested objects, output schema provided), the description fully covers all aspects: input variants, edge cases (truncation, fetch failure), and output structure. No questions remain about how to use the tool or interpret results.

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%, but the description adds meaningful context: explains that the parameters are mutually exclusive alternatives, specifies the source of doc_id ('from search_workday_docs'), and gives the exact URL format for html_url. This extra detail helps the agent understand how to choose and provide valid inputs.

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 description clearly states the verb ('Fetch'), resource ('full markdown for one Workday documentation page'), and distinguishes from sibling tools like browse_workday_toc and search_workday_docs by specifying it retrieves a single page's content. The return fields are listed, leaving no ambiguity about the tool's purpose.

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?

Explicitly says to use either doc_id or html_url, with clear sourcing from sibling tool search_workday_docs. It also notes that html_url is always returned for linking even if body fetch fails. While 'when not to use' is implicit (e.g., don't use for browsing or searching), the guidance is sufficient for an agent to correctly select and invoke the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/philippesimard00/workday-docs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server