Retrieve a paginated list of GitHub Codespaces for the authenticated account without connecting or starting them. Use it to inspect existing workspaces.
List one page of existing Codespaces for the authenticated account. Does not connect or start.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| locale | No | en |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0-alpha.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the 'does not connect or start' behavioral boundary, which is useful, but does not mention pagination behavior or rate limits despite listing 'one page'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the core action and immediately followed by the key exclusion. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. For a simple read-only list tool with annotations covering safety, the description is nearly complete; only pagination behavior and the meaning of the page/locale parameters remain unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 but only says 'one page', loosely implying the page parameter. It says nothing about locale or page bounds. Baseline consideration for low schema coverage suggests the description should do more, but it adds at least marginal meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (Codespaces) scoped to the authenticated account. It does distinguish itself from siblings by noting it 'does not connect or start', implicitly separating it from connection/startup operations, though no sibling is named explicitly like codespace_prepare or codespace_release.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'Does not connect or start' clause implies when NOT to use it, but there is no explicit when-to-use guidance or named alternative for connection/startup tasks. Usage context is only implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.