Skip to main content
Glama

prismic_get_shared_slice

Retrieve a Shared Slice model by its unique ID from Prismic to access reusable content components for building consistent website layouts.

Instructions

Get one Shared Slice model by ID.

Uses GET /slices/{id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slice_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the logic to fetch a Prismic shared slice by ID.
    async def handle_prismic_get_shared_slice(
        *,
        slice_id: str,
        service_factory: ServiceFactory = _build_service,
    ) -> dict[str, Any]:
        """Return one Shared Slice model by ID from Prismic Custom Types API."""
    
        async with service_factory(require_write_credentials=True) as service:
            shared_slice = await service.get_shared_slice_model(slice_id=slice_id)
    
        return {"shared_slice": shared_slice}
  • The MCP tool registration for 'prismic_get_shared_slice'.
    @server.tool(name="prismic_get_shared_slice")
    async def prismic_get_shared_slice(slice_id: str) -> dict[str, Any]:
        """Get one Shared Slice model by ID.
    
        Uses `GET /slices/{id}`.
        """
    
        return await handle_prismic_get_shared_slice(slice_id=slice_id)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the HTTP method ('GET'), implying a read-only operation, but lacks details on authentication needs, rate limits, error handling, or what happens if the ID is invalid. This is a significant gap for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, with two sentences that directly state the purpose and HTTP method. There is zero waste or redundancy, making it efficient and easy to parse for an AI agent.

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 the tool's low complexity (one parameter) and the presence of an output schema, the description is somewhat complete but lacks depth. It covers the basic action and method but misses behavioral context (e.g., permissions, errors) and usage guidelines. With no annotations, it should do more to compensate, but the output schema reduces the need to explain return values.

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

Parameters3/5

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

The description adds minimal meaning beyond the input schema, which has 0% description coverage. It implies 'slice_id' is used to fetch a specific shared slice, but doesn't clarify format, constraints, or examples. With one parameter and an output schema present, the baseline is 3, as the schema handles structure, but the description doesn't compensate for the lack of schema descriptions.

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 action ('Get') and resource ('one Shared Slice model by ID'), making the purpose specific and understandable. It distinguishes from sibling 'prismic_get_shared_slices' (plural) by specifying retrieval of a single item, though it doesn't explicitly contrast with other siblings like 'prismic_insert_shared_slice' or 'prismic_update_shared_slice'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid slice ID), exclusions, or comparisons to siblings like 'prismic_get_shared_slices' for multiple slices or 'prismic_get_document' for documents. The description only states what it does, not when to apply it.

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