WebCake Storefront MCP

get_collection

Read-only

Retrieve a collection's full schema and records by ID to validate fields, types, constraints, and references for storefront page building.

Instructions

Get a specific collection's details including full schema (field names, types, constraints, references) and records

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Collection ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.31.8Aug 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, so the description gets a lower bar. It usefully discloses the response content (full schema plus records), which is real added value, but omits that records may be returned unbounded/unpaginated and says nothing about behavior when the id does not exist.

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 the head verb and resource first, followed by the payload contents. The parenthetical enumeration is slightly dense but every element earns its place by telling the agent what comes back.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so by listing the schema facets and records. What is missing is scale/volume behavior for the records portion and error behavior for an invalid id, which would matter for an agent fetching a record-bearing collection.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'Collection ID' fully. The description adds no format hints (e.g., slug vs numeric id) beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb+resource ('Get a specific collection') and enumerates what the payload contains (schema fields, types, constraints, references, plus records). This clearly separates it from create_collection/update_collection_columns, but it never names or contrasts with the closest siblings list_collections and query_collection_records.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as list_collections (for enumeration) or query_collection_records (for filtered record retrieval). The agent must infer from the name that this is the 'one collection by id' lookup.

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

Deploy Server