Skip to content

Commit 4fd8cef

Browse files
committed
Update completion.md
1 parent 5ba9ba2 commit 4fd8cef

File tree

1 file changed

+9
-14
lines changed

1 file changed

+9
-14
lines changed

docs/specification/server/utilities/completion.md

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,15 @@ title: Completion
66
**Protocol Revision**: {{< param protocolRevision >}}
77
{{< /callout >}}
88

9-
The Model Context Protocol (MCP) provides a standardized way for servers to provide argument completion suggestions for prompts and resource URIs. This enables rich, IDE-like experiences where users receive contextual suggestions while entering argument values.
9+
The Model Context Protocol (MCP) provides a standardized way for servers to offer argument autocompletion suggestions for prompts and resource URIs. This enables rich, IDE-like experiences where users receive contextual suggestions while entering argument values.
1010

1111
## User Interaction Model
1212

13-
Completion in MCP is designed to support interactive user experiences similar to IDE code completion. A recommended implementation pattern is showing completion suggestions in a dropdown or popup menu as users type, with the ability to filter and select from available options.
13+
Completion in MCP is designed to support interactive user experiences similar to IDE code completion.
1414

15-
However, implementations are free to expose completion through any interface pattern that suits their needs - the protocol itself does not mandate any specific user interaction model.
15+
For example, applications may show completion suggestions in a dropdown or popup menu as users type, with the ability to filter and select from available options.
16+
17+
However, implementations are free to expose completion through any interface pattern that suits their needs&mdash;the protocol itself does not mandate any specific user interaction model.
1618

1719
## Protocol Messages
1820

@@ -61,7 +63,7 @@ The protocol supports two types of completion references:
6163
| Type | Description | Example |
6264
|------|-------------|---------|
6365
| `ref/prompt` | References a prompt by name | `{"type": "ref/prompt", "name": "code_review"}` |
64-
| `ref/resource` | References a resource URI | `{"type": "ref/resource", "uri": "file://{path}"}` |
66+
| `ref/resource` | References a resource URI | `{"type": "ref/resource", "uri": "file:///{path}"}` |
6567

6668
### Completion Results
6769

@@ -103,28 +105,21 @@ sequenceDiagram
103105

104106
## Implementation Considerations
105107

106-
1. Servers SHOULD:
108+
1. Servers **SHOULD**:
107109
- Return suggestions sorted by relevance
108110
- Implement fuzzy matching where appropriate
109111
- Rate limit completion requests
110112
- Validate all inputs
111113

112-
2. Clients SHOULD:
114+
2. Clients **SHOULD**:
113115
- Debounce rapid completion requests
114116
- Cache completion results where appropriate
115117
- Handle missing or partial results gracefully
116118

117119
## Security
118120

119-
Implementations MUST:
121+
Implementations **MUST**:
120122
- Validate all completion inputs
121123
- Implement appropriate rate limiting
122124
- Control access to sensitive suggestions
123125
- Prevent completion-based information disclosure
124-
125-
## See Also
126-
127-
{{< cards >}}
128-
{{< card link="/server/prompts" title="Prompts" icon="chat" >}}
129-
{{< card link="/server/resources" title="Resources" icon="document" >}}
130-
{{< /cards >}}

0 commit comments

Comments
 (0)