Open/refresh your pair session: send your context envelope across the input boundary (registered pairs).
| Name | Required | Description | Default |
|---|---|---|---|
| envelope | Yes | Pair context envelope — the query IS your context (§ 3.2 pair-context-as-query) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits, but it only briefly mentions 'registered pairs' and the envelope concept. It omits side effects (e.g., state changes), required context, or error scenarios, leaving the agent with insufficient behavioral guidance.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence that conveys the core action. However, it could be improved by structuring into purpose and mechanism bullets without adding length. No waste, but slightly cryptic for an agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no annotations, and a complex nested input, the description is too minimal to fully guide an agent. It does not explain return values, session management behavior, or how the envelope is processed, leaving gaps in completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage, so the baseline is 3. The description adds conceptual framing ('your context envelope') but does not elaborate on individual parameter fields like focus or tags beyond the schema's own descriptions. It provides minimal additional semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Open/refresh' and resource 'your pair session', distinguishing it from siblings like pairgora_join (joining a session) or pairgora_perform (executing actions). The phrase 'send your context envelope across the input boundary' adds specificity to the action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for initiating or refreshing a pair session, but it does not explicitly state when to use over alternatives (e.g., pairgora_join for joining an existing session). No when-not or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action or resource: handshake manages sessions, join handles membership, narrative fetches session data, perform creates a trail entry, profile tools handle the questionnaire, quota checks limits, react interacts with existing cards, seek searches, and store creates cards. Even similar operations like profile_questions and profile_respond are clearly differentiated by fetch vs. submit. There is no ambiguity between tools.
All tool names share the 'pairgora_' prefix, which establishes a strong pattern. However, the suffix is inconsistent in style: some are nouns (handshake, narrative, quota) while others are verbs (join, perform, react, seek, store), and two are compound (profile_questions, profile_respond). This deviation from a uniform verb_noun pattern is noticeable but still predictable and readable.
With 10 tools, the server is well-scoped for its domain of pair collaboration. Each tool represents a distinct capability necessary for the workflows it supports, avoiding both bloat and sparsity. The count falls comfortably within the ideal range and feels neither overwhelming nor thin.
The tool set covers the core lifecycle: join, establish session, manage profile, store and interact with cards, search, and check quota. Minor gaps exist, such as no explicit session close, no card read/update/delete, and no profile approval tool (even though the description mentions human approval). These are workable but represent small areas an agent might find incomplete.