@@ -276,7 +276,7 @@ Here's how to use this extension:
276
276
x-speakeasy-mcp:
277
277
name: "driver_fastest_lap_tool"
278
278
description: "Find the fastest lap time a driver has ever recorded at any track"
279
- scope : [read, performance-stats]
279
+ scopes : [read, performance-stats]
280
280
` ` ` `
281
281
282
282
#### Customize tool names and descriptions
@@ -330,18 +330,18 @@ paths:
330
330
get:
331
331
summary: List all drivers
332
332
x-speakeasy-mcp:
333
- scope : [read]
333
+ scopes : [read]
334
334
# ...
335
335
post:
336
336
summary: Create a new driver
337
337
x-speakeasy-mcp:
338
- scope : [write]
338
+ scopes : [write]
339
339
# ...
340
340
"/drivers/{driver_id}":
341
341
delete:
342
342
summary: Delete a driver
343
343
x-speakeasy-mcp:
344
- scope : [write, destructive]
344
+ scopes : [write, destructive]
345
345
# ...
346
346
` ` `
347
347
@@ -387,11 +387,11 @@ To apply scopes consistently across many operations, you can use the global `x-s
387
387
x-speakeasy-mcp:
388
388
scope-mapping:
389
389
- pattern: "^get|^list"
390
- scope : [read]
390
+ scopes : [read]
391
391
- pattern: "^create|^update"
392
- scope : [write]
392
+ scopes : [write]
393
393
- pattern: "^delete"
394
- scope : [write, destructive]
394
+ scopes : [write, destructive]
395
395
` ` `
396
396
397
397
This automatically applies scopes based on operation name patterns, saving you from manually tagging each endpoint.
@@ -432,7 +432,7 @@ When using MCP, it's essential to provide clear descriptions for each operation.
432
432
Fetch complete details about a specific racing driver including their
433
433
name, team, career statistics, and full history of lap times across all tracks.
434
434
Use this tool when you need comprehensive information about a driver.
435
- scope : [read, driver-info]
435
+ scopes : [read, driver-info]
436
436
parameters:
437
437
- name: driver_id
438
438
in: path
0 commit comments