Machine-readable identifier used in MCP tool calls. Only lowercase letters, numbers and underscores. Cannot be changed after publishing.
+
Machine-readable identifier used in MCP tool calls. Only lowercase letters, numbers and underscores. Cannot be changed after publishing.
-
Human-readable name shown in the console and audit log.
+
Human-readable name shown in the console and audit log.
-
Short imperative sentence shown in the MCP tool manifest.
+
Short imperative sentence shown in the MCP tool manifest.
-
LLM-facing description. Be precise — this is the primary signal the model uses to decide whether to invoke this tool.
+
LLM-facing description. Be precise — this is the primary signal the model uses to decide whether to invoke this tool.
@@ -68,10 +68,8 @@
-
Writing effective descriptions
-
- Start with a verb ("Creates", "Fetches", "Updates"). Mention key input requirements. Describe what a successful response looks like. Avoid vague phrasing like "handles" or "manages". See description best practices →
-
+
Writing effective descriptions
+
Start with a verb ("Creates", "Fetches", "Updates"). Mention key input requirements. Describe what a successful response looks like. Avoid vague phrasing like "handles" or "manages". See description best practices →
@@ -84,10 +82,10 @@
-
Input schema
-
Parameters the LLM passes when calling this tool
+
Input schema
+
Parameters the LLM passes when calling this tool
- JSON Schema draft-07
+ JSON Schema draft-07
@@ -122,10 +120,10 @@
-
Output schema
-
Shape of the data returned to the LLM after a successful call
+
Output schema
+
Shape of the data returned to the LLM after a successful call
- JSON Schema draft-07
+ JSON Schema draft-07
@@ -153,10 +151,8 @@
-
Schemas are protocol-agnostic
-
- These schemas describe the MCP contract, not the upstream wire format. Field mapping in Step 5 translates between the two. You can upload a sample JSON response to auto-generate the output schema.
-
+
Schemas are protocol-agnostic
+
These schemas describe the MCP contract, not the upstream wire format. Field mapping in Step 5 translates between the two. You can upload a sample JSON response to auto-generate the output schema.
- Live validation and publishing
+ Live validation and publishing
@@ -98,7 +98,7 @@ tls:
-
Draft actions
+
Draft actions
@@ -109,8 +109,8 @@ tls:
-
Live actions save the draft first
-
Sample uploads, test runs, YAML actions, publish and gRPC descriptor discovery all persist the current draft before calling the backend.
+
Live actions save the draft first
+
Sample uploads, test runs, YAML actions, publish and gRPC descriptor discovery all persist the current draft before calling the backend.
@@ -123,14 +123,14 @@ tls:
-
Samples and draft generation
-
Persist input/output samples, then generate schemas and mappings from real payloads.
+
Samples and draft generation
+
Persist input/output samples, then generate schemas and mappings from real payloads.
-
+
-
+
- Save input sample
- Save output sample
- Generate draft from samples
+ Save input sample
+ Save output sample
+ Generate draft from samples
@@ -161,13 +161,13 @@ tls:
-
Test run
-
Run the current draft against the upstream before publishing it.
+
Test run
+
Run the current draft against the upstream before publishing it.
-
+
- Run test
- Use response as output sample
+ Run test
+ Use response as output sample
-
+
-
+
-
+
@@ -204,16 +204,16 @@ tls:
-
gRPC descriptor set
-
Upload a compiled descriptor set and discover unary methods from the saved draft.
+
gRPC descriptor set
+
Upload a compiled descriptor set and discover unary methods from the saved draft.
- Choose descriptor set
- Upload and discover services
- No descriptor set selected
+ Choose descriptor set
+ Upload and discover services
+ No descriptor set selected
@@ -228,20 +228,20 @@ tls:
-
YAML import and export
-
Move operation drafts between environments without leaving the wizard.
+
YAML import and export
+
Move operation drafts between environments without leaving the wizard.
Save the current draft and expose it to published agents.
+
Publish
+
Save the current draft and expose it to published agents.
-
Publishing uses the current draft version from this wizard session.
+
Publishing uses the current draft version from this wizard session.
- Publish operation
+ Publish operation
@@ -272,10 +272,8 @@ tls:
-
Operation stays editable in this wizard
-
- Saving creates or updates the current draft in place. Use the live actions above to upload samples, test the draft, export or import YAML, and publish when the upstream contract is ready.
-
+
Operation stays editable in this wizard
+
Saving creates or updates the current draft in place. Use the live actions above to upload samples, test the draft, export or import YAML, and publish when the upstream contract is ready.