context-crystal

Overview Schema Source Related Servers Discussions Admin

crystal_extension_list

Discovers and lists extensions across host, cave, and crystal scopes, enabling inspection of embedded modules and drop-ins with optional scope filtering and JSON output.

Instructions

Discover and list extensions across the 3-tier scoping cascade (host, cave, crystal) including embedded Scala Native modules and declarative/executable drop-ins.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crystal_extension_list"
  }
}

Input Schema

Name	Required	Description
`scope`	No	Filter by scope: host, cave, or crystal
`crystal_id`	No	Optional crystal ID to inspect crystal-scoped extensions and state
`json_output`	No	Return raw JSON manifest array instead of formatted summary (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.3.0Oct 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 'Discover and list' implies a read-only, non-mutating operation and it discloses which artifacts are covered (embedded Scala Native modules, declarative/executable drop-ins), but it says nothing about output shape, ordering, or whether the result is scoped/paginated.

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?

A single front-loaded sentence with no filler; the scope model is stated before the artifact types. The dense domain jargon ('drop-ins', 'scoping cascade') costs a bit of clarity for an outsider.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter listing tool with no output schema, the description covers what is enumerated but omits return format, whether results aggregate across scopes by default, and how crystal_id interacts with scope. Adequate but with real gaps for an agent deciding what to expect.

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%, so the baseline is 3, but the description adds real meaning by explaining the '3-tier scoping cascade (host, cave, crystal)' concept that the 'scope' enum refers to. It does not mention crystal_id or json_output, so it does not fully compensate beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb pair ('Discover and list') with a clearly named resource (extensions) and scope (host/cave/crystal cascade). It implicitly separates itself from management siblings (extension_manage/run/call) by being the discovery operation, though it never names them.

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

Usage Guidelines3/5

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

Usage is only implied: 'Discover and list' suggests calling this before manage/run/call, but there is no explicit when-to-use, no prerequisites, and no alternatives named among the many crystal_extension_* siblings.

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