Skip to main content
Glama

prismic_get_shared_slices

Retrieve all Shared Slice models from Prismic's Custom Types API to manage reusable content components in your projects.

Instructions

List all Shared Slice models from Prismic Custom Types API.

Uses GET /slices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core logic function that fetches all Shared Slice models.
    async def handle_prismic_get_shared_slices(
        *,
        service_factory: ServiceFactory = _build_service,
    ) -> dict[str, Any]:
        """Return all Shared Slice models from Prismic Custom Types API."""
    
        async with service_factory(require_write_credentials=True) as service:
            shared_slices = await service.get_all_shared_slice_models()
    
        return {"shared_slices": shared_slices}
  • The registration of the tool in the MCP server, which calls the handler.
    @server.tool(name="prismic_get_shared_slices")
    async def prismic_get_shared_slices() -> dict[str, Any]:
        """List all Shared Slice models from Prismic Custom Types API.
    
        Uses `GET /slices`.
        """
    
        return await handle_prismic_get_shared_slices()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a list operation and mentions the API endpoint, but doesn't disclose important behavioral traits: whether this requires authentication, rate limits, pagination behavior, error conditions, or what format the output takes. The description is minimal and leaves critical operational context unspecified.

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?

The description is appropriately concise with two short sentences. The first sentence states the purpose clearly, and the second provides implementation detail. There's no wasted text, though the structure could be slightly improved by integrating the API endpoint information more naturally with the purpose statement.

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?

Given that this is a read operation (implied by 'List') with 0 parameters and an output schema exists, the description is minimally adequate. However, with no annotations and multiple sibling tools, it should provide more context about when to use it and what behavioral constraints exist. The presence of an output schema means return values are documented elsewhere, but operational context is lacking.

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?

The tool has 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters, and it appropriately doesn't mention any. The baseline for 0 parameters is 4, and the description doesn't incorrectly suggest parameters exist.

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?

The description clearly states the tool's purpose: 'List all Shared Slice models from Prismic Custom Types API.' This specifies the verb ('List'), resource ('Shared Slice models'), and source ('Prismic Custom Types API'). However, it doesn't explicitly differentiate from sibling tools like 'prismic_get_shared_slice' (singular) or 'prismic_get_types', which might have overlapping functionality.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools like 'prismic_get_shared_slice' (singular) and 'prismic_get_types', there's no indication of when this list-all operation is appropriate versus more specific queries. The mention of 'Uses GET /slices' is technical implementation detail, not usage guidance.

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/rahulpowar/prismic-content-mcp'

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