Skip to main content
Glama

Look up an Extend component / function reference

lookup_extend_reference
Read-onlyIdempotent

Find the best-matching Extend app reference page with inline content for building PMD widgets, model components, functions, or scripting. Ground your code in authoritative schema and signatures.

Instructions

Ground Extend app-building in the authoritative reference. Given what you're trying to build or use, this returns the BEST-matching reference page WITH its content inline (excerpt) — not just a pointer — plus alternative pointers. Use this before writing PMD/widget/scripting code so you ground on the real schema/signature instead of guessing.

Scoped to the "Extend App Components Reference" (PMD tags/widgets, model components, PMD functions, PMD scripting). For broader/conceptual docs use search_workday_docs. Best results require the full-text index (npm run build-index).

Args:

  • intent (string): what you want to build/use, e.g. "sortable grid with row actions", "function to format a date", "validate a field before submit"

  • kind ('any' | 'component' | 'function' | 'scripting'): narrow the scope (default 'any') component = PMD tags/widgets + model components; function = PMD functions; scripting = PMD scripting tags

  • alternatives (number): how many additional pointers to return, 0-10 (default 4)

Returns: { intent, kind, engine, best: { doc_id, title, breadcrumb, html_url, excerpt, truncated } | null, alternatives: [{ doc_id, title, breadcrumb, html_url, score }] } If best is null, nothing matched the scope — widen kind, rephrase, or use search_workday_docs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesWhat you want to build/use, e.g. 'sortable grid with row actions'
kindNoNarrow scope: component | function | scripting | anyany
alternativesNoNumber of additional pointers to return (0-10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYes
kindYes
engineYes
bestYes
alternativesYes
Behavior5/5

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

Annotations provide readOnlyHint, idempotentHint, etc. Description adds value by explaining the tool returns excerpts inline, mentions the full-text index requirement, and describes the return structure, going beyond annotations.

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?

Description is front-loaded with purpose and usage, but contains some redundancy (e.g., repeats scope). However, every sentence is valuable and it remains clear. Minor room for conciseness improvement.

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 complexity (3 params, output schema, annotations), the description covers purpose, usage, behavior, parameters, and return values completely. Output schema documents return structure, so no gaps.

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

Parameters5/5

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

Schema coverage is 100%, and the description enriches each parameter with examples (intent), detailed enum breakdown (kind), and explicit range/default (alternatives), adding meaning beyond the schema.

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 it returns the best-matching reference page with inline content and alternative pointers, and distinguishes itself from siblings by scoping to the 'Extend App Components Reference' and directing broader queries to search_workday_docs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises using this tool before writing code to ground on real schema/signature, and specifies when to use search_workday_docs for broader/conceptual docs, providing clear usage context and alternatives.

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