Skip to main content
Glama
Sign In
ChatGPT Context Bridge

ChatGPT Context Bridge

by howdycarter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Propose Notion Page

propose_notion_page
Idempotent

Create a draft Notion payload with verification notes for a staged chat, without modifying Notion.

Instructions

Create a staged Notion payload with verification notes for one staged chat. Draft-only; no Notion API calls or page mutations.

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": {
      "staged_chat_id": "<staged_chat_id>"
    },
    "name": "propose_notion_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
staged_chat_idYesID returned by stage_chat or search_context.
response_formatNoOutput format: markdown or json.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations include idempotentHint=true and destructiveHint=false; description adds crucial context that this is draft-only with no Notion API calls or page mutations, clarifying that any side effects are local payload creation only. This goes beyond what annotations alone convey.

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?

Single concise sentence, front-loaded with the verb and purpose. No wasted words, and it includes the key safety qualifier ('Draft-only') in the same sentence.

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?

Given the tool's moderate complexity and full schema coverage, the description conveys the main purpose and critical constraints. It lacks an explicit statement of the return value, but the response_format parameter implies the output format, and the tool name/content fill the 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 descriptions cover both parameters (staged_chat_id and response_format) at 100%, so the description doesn't need to add parameter details. It references 'one staged chat' which aligns with staged_chat_id but adds no new semantic meaning.

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 states a specific action ('Create a staged Notion payload') with a clear resource and scope ('for one staged chat'). It also distinguishes from siblings by indicating draft-only and no API calls, differentiating from propose_homebase_note.

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?

Provides clear context: it should be used when you have a staged chat and want a payload. However, it does not explicitly mention when not to use it or alternatives like propose_homebase_note, so it falls short of full exclusion guidance.

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

Deploy Server

Other Tools