mcp-chat-cards

Overview Schema Source Related Servers Discussions Admin

Start an efficient prompt

create_prompt_gist_card

Creates a card that asks the user to describe their prompt goal in up to 350 characters, then returns the gist with the next-step rules for the efficient-prompt flow.

Instructions

Open step 1 of the efficient-prompt flow: a card asking the user to describe, in no more than 350 characters, the gist of where they want to go. Call this when a message is tagged [efficient-prompt], or when the user asks for help writing a prompt. Submitting the card sends back the gist along with the rules for the rest of the flow, so answer with the card and wait rather than asking follow-up questions in chat.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No
`question`	No	Replaces the default gist question when you already know what they are circling
`subtitle`	No
`placeholder`	No	Placeholder text inside the gist textarea
`contextActions`	No	Right-click menu actions the model anticipates being useful. Choosing one sends its prompt to the conversation; use {{selection}} to include the user's selected text.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`card`	Yes
`parts`	Yes	Split state, present on EVERY card result so one completeness check works for all card types. Cards that cannot split always report {current:1,total:1,hasMore:false}; create_markdown_card and create_code_tour_card pack oversized content into parts and can report more. Read hasMore rather than the card title to decide whether content was withheld.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0-alphaAug 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it does well: it explains this is step 1, that submitting sends back the gist plus rules, and instructs the agent to answer with the card and wait. It could add detail on what the resulting card contains visually or how the next flow step is triggered, but the core behavior is disclosed.

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?

Three sentences, each with a distinct job: what the tool does, when to call it, and how to behave after calling it. The description is front-loaded with the action and contains no filler.

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?

For a simple card-generation tool with an output schema, the description covers the key context: flow position, trigger conditions, character limit, and follow-up behavior. It leaves the relationship to create_efficient_prompt_card and create_prompt_refine_card implicit, which is the main completeness gap.

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?

Schema coverage is 60%, with question, placeholder, and contextActions documented. The description adds flow context but does not explain the remaining title and subtitle parameters or map them to behavior. It is adequate because the purpose of the card clarifies why fields exist, but there is a clear gap for undocumented parameters.

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

Purpose5/5

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

The description uses a specific verb and resource: 'Open step 1 of the efficient-prompt flow' and a card asking for the gist in no more than 350 characters. This clearly identifies the tool as the entry point of the prompt flow and distinguishes it from later flow steps and sibling card tools.

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

Usage Guidelines4/5

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

It states explicit triggers: 'when a message is tagged [efficient-prompt], or when the user asks for help writing a prompt.' It gives behavioral instructions to use the card and wait, but does not explicitly contrast this tool with close siblings such as create_prompt_refine_card or create_efficient_prompt_card, so it stops short of full exclusions.

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