Skip to main content
Glama
Sign In
ChatGPT Context Bridge

ChatGPT Context Bridge

by howdycarter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search Staged Context

search_context
Read-onlyIdempotent

Search staged ChatGPT Context Bridge records by querying titles, tags, and summaries, returning chat IDs, titles, summaries, and draft paths for review.

Instructions

Search private Context Bridge staging records. Read-only. Returns staged chat IDs, titles, summaries, and draft paths when present.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum staged records to return.
queryNoSearch staged chat titles, tags, and summaries.
offsetNoNumber of matching records to skip.
response_formatNoOutput format: markdown or json.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds that the tool is private and returns specific fields, which is useful behavioral context beyond what annotations provide. There is no contradiction, and the description enriches understanding of the search scope.

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 two concise sentences, front-loaded with the core action ('Search private Context Bridge staging records') and includes only necessary detail about return values. Every word earns its place.

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

Completeness5/5

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

For a simple filtered search tool with no output schema, the description adequately conveys purpose and return structure. It complements the well-documented schema by explaining what is returned, making the tool understandable in context.

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 100% of parameters, so the schema already fully explains all four parameters (limit, query, offset, response_format). The description adds no additional parameter-level detail, so the baseline score of 3 is appropriate.

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 clearly states the verb 'Search' and the resource 'private Context Bridge staging records', and specifies the returned fields (chat IDs, titles, summaries, draft paths). This distinguishes it from sibling tools like stage_chat or summarize_thread, which create or process context.

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?

The description clearly indicates this tool is for searching staged records and is read-only, providing context that differentiates it from sibling tools that create or modify data. However, it does not explicitly mention when not to use it or name specific alternatives, so it falls short of a full explicit exclusion.

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