modelcontextprotocol/inspector
Watch
1
0
Fork
You've already forked inspector
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: describe DirectoryReadResultSchema as the shape both eras share (#2374 review)

Browse source 
Its doc comment still called it the legacy result, though both eras now
parse with it once the codec has removed resultType.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q3RsrgCxVoFPokLB4vAkxi
Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-09-14 09:25:16 -04:00
commit f3e0edd257
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
core/mcp/skillsSchemas.ts
View file

@ -235,8 +235,10 @@ export type GetSkillResult = SkillEntry;
export const DirectoryChildSchema = ResourceSchema; export const DirectoryChildSchema = ResourceSchema;
/** /**
* `resources/directory/read` result on a **legacy** connection: the directory's * `resources/directory/read` result on **either** era: the directory's direct
* direct children plus the opaque cursor. * children plus the opaque cursor. On a modern connection this is the shape
* after the SDK codec has checked and removed `resultType`, which is why no
* modern variant exists — see the note below (#2373).
* *
* `looseObject`, matching every other result schema here: a server that also * `looseObject`, matching every other result schema here: a server that also
* sends the caching attributes is not wrong for doing so, and a schema is not * sends the caching attributes is not wrong for doing so, and a schema is not