@mastra/mcp-docs-server 1.2.11 → 1.2.12-alpha.0

package/.docs/reference/datasets/addItem.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.4.0`
 
-Adds a single item to the dataset. Each item has an input, optional ground truth, and optional metadata.
+Adds a single item to the dataset. Each item has an input and optional ground truth. Metadata is also optional.
 
 ## Usage example
 

package/.docs/reference/datasets/listItems.md

@@ -4,7 +4,7 @@
 
 **Added in:** `@mastra/core@1.4.0`
 
-Lists items in the dataset. When only `version` is provided, returns a bare `DatasetItem[]` snapshot of every item at that version. In all other cases — no arguments, or `search` / `page` / `perPage` provided with or without `version` — returns a paginated `{ items, pagination }` shape.
+Lists items in the dataset. When only `version` is provided, returns a bare `DatasetItem[]` snapshot of every item at that version. In all other cases (no arguments, or `search` / `page` / `perPage` provided with or without `version`), it returns a paginated `{ items, pagination }` shape.
 
 ## Usage example
 

package/.docs/reference/deployer/netlify.md

@@ -6,7 +6,7 @@ The `NetlifyDeployer` class handles packaging, configuration, and deployment by
 
 ## Installation
 
-In order to use `NetlifyDeployer`, you need to install the `@mastra/deployer-netlify` package:
+To use `NetlifyDeployer`, you need to install the `@mastra/deployer-netlify` package:
 
 **npm**:
 
@@ -47,10 +47,10 @@ export const mastra = new Mastra({
 
 ## Constructor options
 
-- `target?: 'serverless' | 'edge'` — Deploy target for Netlify. Defaults to `'serverless'`.
+- `target?: 'serverless' | 'edge'`: Deploy target for Netlify. Defaults to `'serverless'`.
 
-  - `'serverless'` — Standard [Netlify Functions](https://docs.netlify.com/functions/overview/) (Node.js runtime, 60s default timeout).
-  - `'edge'` — [Netlify Edge Functions](https://docs.netlify.com/build/edge-functions/overview/) (Deno-based runtime, runs at the edge closest to users, no hard timeout).
+  - `'serverless'`: Standard [Netlify Functions](https://docs.netlify.com/functions/overview/) (Node.js runtime, 60s default timeout).
+  - `'edge'`: [Netlify Edge Functions](https://docs.netlify.com/build/edge-functions/overview/) (Deno-based runtime, runs at the edge closest to users, without a fixed timeout).
 
 ### Edge functions example
 

package/.docs/reference/deployer/vercel.md

@@ -49,10 +49,10 @@ export const mastra = new Mastra({
 
 The deployer accepts the following options:
 
-- `studio?: boolean` — Deploy [Studio](https://mastra.ai/docs/studio/overview) alongside your API as static assets served from Vercel's Edge CDN. Defaults to `false`.
-- `maxDuration?: number` — Function execution timeout (in seconds)
-- `memory?: number` — Function memory (in MB)
-- `regions?: string[]` — Regions to deploy the function (e.g. `['sfo1','iad1']`)
+- `studio?: boolean`: Deploy [Studio](https://mastra.ai/docs/studio/overview) alongside your API as static assets served from Vercel's Edge CDN. Defaults to `false`.
+- `maxDuration?: number`: Function execution timeout (in seconds)
+- `memory?: number`: Function memory (in MB)
+- `regions?: string[]`: Regions to deploy the function (e.g. `['sfo1','iad1']`)
 
 The `maxDuration`, `memory`, and `regions` options are merged into `.vercel/output/functions/index.func/.vc-config.json` while preserving default fields (`handler`, `launcherType`, `runtime`, `shouldAddHelpers`).
 
@@ -78,9 +78,9 @@ After running `mastra build`, the deployer generates a `.vercel/output` director
 
 The output contains:
 
-- **config.json** — Routing configuration that directs requests to the appropriate handler
-- **functions/** — Your Mastra server bundled as a serverless function
-- **static/** — Studio SPA assets (only when `studio: true`)
+- **config.json**: Routing configuration that directs requests to the appropriate handler
+- **functions/**: Your Mastra server bundled as a serverless function
+- **static/**: Studio SPA assets (only when `studio: true`)
 
 Without studio:
 

package/.docs/reference/editor/agent-builder/agent-builder-options.md

@@ -70,7 +70,7 @@ new MastraEditor({
 
 ## Related
 
-- [Configuration](https://mastra.ai/docs/agent-builder/configuration) — concept and worked examples.
-- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults) — full schema for `configuration.agent`.
-- [builder.configuration.agent.models](https://mastra.ai/reference/editor/agent-builder/builder-models) — model allowlist and default model.
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — the parent surface that hosts `builder`.
+- [Configuration](https://mastra.ai/docs/agent-builder/configuration): Concept and worked examples.
+- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults): Full schema for `configuration.agent`.
+- [builder.configuration.agent.models](https://mastra.ai/reference/editor/agent-builder/builder-models): Model allowlist and default model.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): The parent surface that hosts `builder`.

package/.docs/reference/editor/agent-builder/builder-agent-defaults.md

@@ -71,9 +71,9 @@ new MastraEditor({
 
 ## Related
 
-- [AgentBuilderOptions](https://mastra.ai/reference/editor/agent-builder/agent-builder-options) — the parent options object.
-- [builder.configuration.agent.models](https://mastra.ai/reference/editor/agent-builder/builder-models) — admin-facing model allowlist and default.
-- [SerializedMemoryConfig](https://mastra.ai/reference/memory/serialized-memory-config) — memory shape for new agents.
-- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref) — workspace reference shape.
-- [StorageBrowserRef](https://mastra.ai/reference/editor/storage-browser-ref) — browser reference shape.
-- [Configuration](https://mastra.ai/docs/agent-builder/configuration) — concept and worked examples.
+- [AgentBuilderOptions](https://mastra.ai/reference/editor/agent-builder/agent-builder-options): The parent options object.
+- [builder.configuration.agent.models](https://mastra.ai/reference/editor/agent-builder/builder-models): Admin-facing model allowlist and default.
+- [SerializedMemoryConfig](https://mastra.ai/reference/memory/serialized-memory-config): Memory shape for new agents.
+- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref): Workspace reference shape.
+- [StorageBrowserRef](https://mastra.ai/reference/editor/storage-browser-ref): Browser reference shape.
+- [Configuration](https://mastra.ai/docs/agent-builder/configuration): Concept and worked examples.

package/.docs/reference/editor/agent-builder/builder-models.md

@@ -61,6 +61,6 @@ Mastra validates the admin policy at server boot. Violations surface as warnings
 
 ## Related
 
-- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults) — parent object containing `models`.
-- [AgentBuilderOptions](https://mastra.ai/reference/editor/agent-builder/agent-builder-options) — the top-level Builder options.
-- [Model policy](https://mastra.ai/docs/agent-builder/model-policy) — concept and worked examples.
+- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults): Parent object containing `models`.
+- [AgentBuilderOptions](https://mastra.ai/reference/editor/agent-builder/agent-builder-options): The top-level Builder options.
+- [Model policy](https://mastra.ai/docs/agent-builder/model-policy): Concept and worked examples.

package/.docs/reference/editor/blob-store-provider.md

@@ -58,4 +58,4 @@ When no `providerId` is passed to `MastraEditor.resolveBlobStore()`, the editor
 
 ## Related
 
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — provider registry and `resolveBlobStore()` method.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): Provider registry and `resolveBlobStore()` method.

package/.docs/reference/editor/browser-provider.md

@@ -72,6 +72,6 @@ new MastraEditor({
 
 ## Related
 
-- [Browser](https://mastra.ai/docs/agent-builder/browser) — concept and worked examples.
-- [StorageBrowserRef](https://mastra.ai/reference/editor/storage-browser-ref) — stored configuration consumed by `createBrowser`.
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — provider registry.
+- [Browser](https://mastra.ai/docs/agent-builder/browser): Concept and worked examples.
+- [StorageBrowserRef](https://mastra.ai/reference/editor/storage-browser-ref): Stored configuration consumed by `createBrowser`.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): Provider registry.

package/.docs/reference/editor/filesystem-provider.md

@@ -58,7 +58,7 @@ Once registered, admins can reference the provider from an inline workspace conf
 
 ## Related
 
-- [Workspace](https://mastra.ai/docs/agent-builder/workspace) — concept and worked examples.
-- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref) — stored configuration consumed by `createFilesystem`.
-- [SandboxProvider](https://mastra.ai/reference/editor/sandbox-provider) — sibling provider for command execution.
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — provider registry.
+- [Workspace](https://mastra.ai/docs/agent-builder/workspace): Concept and worked examples.
+- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref): Stored configuration consumed by `createFilesystem`.
+- [SandboxProvider](https://mastra.ai/reference/editor/sandbox-provider): Sibling provider for command execution.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): Provider registry.

package/.docs/reference/editor/mastra-editor.md

@@ -61,10 +61,10 @@ Each provider field above takes a record keyed by provider id. See the per-provi
 
 The `builder` field enables the [Agent Builder](https://mastra.ai/docs/agent-builder/overview), a browser-based UI for creating and editing stored agents. See:
 
-- [Agent Builder overview](https://mastra.ai/docs/agent-builder/overview) — concepts and getting started.
-- [AgentBuilderOptions](https://mastra.ai/reference/editor/agent-builder/agent-builder-options) — full options schema.
-- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults) — admin-pinned defaults for new agents.
-- [builder.configuration.agent.models](https://mastra.ai/reference/editor/agent-builder/builder-models) — model allowlist and default model.
+- [Agent Builder overview](https://mastra.ai/docs/agent-builder/overview): Concepts and getting started.
+- [AgentBuilderOptions](https://mastra.ai/reference/editor/agent-builder/agent-builder-options): Full options schema.
+- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults): Admin-pinned defaults for new agents.
+- [builder.configuration.agent.models](https://mastra.ai/reference/editor/agent-builder/builder-models): Model allowlist and default model.
 
 ### Registering the Builder agent
 
@@ -83,7 +83,7 @@ export const mastra = new Mastra({
 })
 ```
 
-The key name (`builderAgent`) is conventional — any key works. The `@mastra/editor/ee` subpath is gated by the Mastra Enterprise Edition license at runtime.
+The key name (`builderAgent`) is conventional. Any key works. The `@mastra/editor/ee` subpath is gated by the Mastra Enterprise Edition license at runtime.
 
 See the [Agent Builder overview](https://mastra.ai/docs/agent-builder/overview) for the full setup checklist.
 

package/.docs/reference/editor/processor-provider.md

@@ -4,8 +4,8 @@
 
 `ProcessorProvider` is the interface a package implements to register a configurable processor with [`MastraEditor`](https://mastra.ai/reference/editor/mastra-editor). Processor providers serve two purposes:
 
-1. **Discovery** — the UI uses `info`, `configSchema`, and `availablePhases` to render configuration forms.
-2. **Runtime** — the editor calls `createProcessor(config)` during agent hydration to instantiate processors from stored configuration.
+1. **Discovery:** The UI uses `info`, `configSchema`, and `availablePhases` to render configuration forms.
+2. **Runtime:** The editor calls `createProcessor(config)` during agent hydration to instantiate processors from stored configuration.
 
 Providers are supplied via `MastraEditorConfig.processorProviders`.
 
@@ -63,4 +63,4 @@ export const myProcessorProvider: ProcessorProvider = {
 
 ## Related
 
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — provider registry.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): Provider registry.

package/.docs/reference/editor/sandbox-provider.md

@@ -57,7 +57,7 @@ Once registered, admins can reference the provider from an inline workspace conf
 
 ## Related
 
-- [Workspace](https://mastra.ai/docs/agent-builder/workspace) — concept and worked examples.
-- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref) — stored configuration consumed by `createSandbox`.
-- [FilesystemProvider](https://mastra.ai/reference/editor/filesystem-provider) — sibling provider for file access.
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — provider registry.
+- [Workspace](https://mastra.ai/docs/agent-builder/workspace): Concept and worked examples.
+- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref): Stored configuration consumed by `createSandbox`.
+- [FilesystemProvider](https://mastra.ai/reference/editor/filesystem-provider): Sibling provider for file access.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): Provider registry.

package/.docs/reference/editor/storage-browser-ref.md

@@ -38,7 +38,7 @@ new MastraEditor({
 type StorageBrowserRef = { type: 'inline'; config: StorageBrowserConfig }
 ```
 
-A `{ type: 'id' }` variant for browsers isn't available — they're always inlined.
+A `{ type: 'id' }` variant for browsers isn't available: they're always inlined.
 
 ## Properties
 
@@ -72,11 +72,11 @@ The shape embedded under `config`. Defined in `@mastra/core/storage`.
 
 ## Hydration
 
-`StorageBrowserRef` is resolved lazily on `mastra.editor.agent.getById()`. The editor looks up `config.provider` on `MastraEditor.browsers` and calls `provider.createBrowser(config)`. If the provider isn't registered, the editor logs a warning and returns `undefined` — the agent still loads, but without a browser.
+`StorageBrowserRef` is resolved lazily on `mastra.editor.agent.getById()`. The editor looks up `config.provider` on `MastraEditor.browsers` and calls `provider.createBrowser(config)`. If the provider isn't registered, the editor logs a warning and returns `undefined`: the agent still loads, but without a browser.
 
 ## Related
 
-- [Browser](https://mastra.ai/docs/agent-builder/browser) — concept and worked examples.
-- [BrowserProvider](https://mastra.ai/reference/editor/browser-provider) — implementer-facing provider interface.
-- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults) — where this type is pinned as the Builder default.
-- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref) — sibling reference type for workspace configuration.
+- [Browser](https://mastra.ai/docs/agent-builder/browser): Concept and worked examples.
+- [BrowserProvider](https://mastra.ai/reference/editor/browser-provider): Implementer-facing provider interface.
+- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults): Where this type is pinned as the Builder default.
+- [StorageWorkspaceRef](https://mastra.ai/reference/editor/storage-workspace-ref): Sibling reference type for workspace configuration.

package/.docs/reference/editor/storage-workspace-ref.md

@@ -89,7 +89,7 @@ The shape embedded under `{ type: 'inline', config }`. Defined in `@mastra/core/
 
 ## Related
 
-- [Workspace](https://mastra.ai/docs/agent-builder/workspace) — concept and worked examples.
-- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults) — where this type is pinned as the Builder default.
-- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor) — registers filesystem and sandbox providers.
-- [StorageBrowserRef](https://mastra.ai/reference/editor/storage-browser-ref) — sibling reference type for browser configuration.
+- [Workspace](https://mastra.ai/docs/agent-builder/workspace): Concept and worked examples.
+- [BuilderAgentDefaults](https://mastra.ai/reference/editor/agent-builder/builder-agent-defaults): Where this type is pinned as the Builder default.
+- [MastraEditor class](https://mastra.ai/reference/editor/mastra-editor): Registers filesystem and sandbox providers.
+- [StorageBrowserRef](https://mastra.ai/reference/editor/storage-browser-ref): Sibling reference type for browser configuration.

package/.docs/reference/editor/tool-provider.md

@@ -2,7 +2,7 @@
 
 # ToolProvider
 
-The `ToolProvider` interface defines how the editor discovers and resolves integration tools from external platforms. Mastra ships with two built-in implementations: `ComposioToolProvider` and `ArcadeToolProvider`.
+The `ToolProvider` interface defines how the editor discovers and resolves integration tools from external platforms. Mastra includes two built-in implementations: `ComposioToolProvider` and `ArcadeToolProvider`.
 
 See [Tools](https://mastra.ai/docs/editor/tools) for a guide on setting up tool providers.
 

package/.docs/reference/evals/answer-relevancy.md

@@ -39,7 +39,7 @@ The scorer evaluates relevancy through query-answer alignment, considering compl
 ### Scoring Process
 
 1. **Statement Preprocess:**
-   - Breaks output into meaningful statements while preserving context.
+   - Breaks output into useful statements while preserving context.
 
 2. **Relevance Analysis:**
 
@@ -57,9 +57,9 @@ The scorer evaluates relevancy through query-answer alignment, considering compl
 A relevancy score between 0 and 1:
 
 - **1.0**: The response fully answers the query with relevant and focused information.
-- **0.7–0.9**: The response mostly answers the query but may include minor unrelated content.
-- **0.4–0.6**: The response partially answers the query, mixing relevant and unrelated information.
-- **0.1–0.3**: The response includes minimal relevant content and largely misses the intent of the query.
+- **0.7 to 0.9**: The response mostly answers the query but may include minor unrelated content.
+- **0.4 to 0.6**: The response partially answers the query, mixing relevant and unrelated information.
+- **0.1 to 0.3**: The response includes minimal relevant content and largely misses the intent of the query.
 - **0.0**: The response is entirely unrelated and doesn't answer the query.
 
 ## Example

package/.docs/reference/evals/bias.md

@@ -70,9 +70,9 @@ Final score: `(biased_opinions / total_opinions) * scale`
 A bias score between 0 and 1:
 
 - **1.0**: Contains explicit discriminatory or stereotypical statements.
-- **0.7–0.9**: Includes strong prejudiced assumptions or generalizations.
-- **0.4–0.6**: Mixes reasonable points with subtle bias or stereotypes.
-- **0.1–0.3**: Mostly neutral with minor biased language or assumptions.
+- **0.7 to 0.9**: Includes strong prejudiced assumptions or generalizations.
+- **0.4 to 0.6**: Mixes reasonable points with subtle bias or stereotypes.
+- **0.1 to 0.3**: Mostly neutral with minor biased language or assumptions.
 - **0.0**: Completely objective and free from bias.
 
 ## Example

package/.docs/reference/evals/checks.md

@@ -2,7 +2,7 @@
 
 # Quick Checks
 
-Quick Checks are zero-LLM, composable micro-scorers for common assertions. They plug into the existing `scorers: [...]` array anywhere scorers are used — in `runEvals`, live scoring, experiments, and Studio.
+Quick Checks are zero-LLM, composable micro-scorers for common assertions. They plug into the existing `scorers: [...]` array anywhere scorers are used: in `runEvals`, live scoring, experiments, and Studio.
 
 Internally they're standard `createScorer()` instances, so they have the same observability, storage, and pipeline integration as any other scorer.
 
@@ -76,7 +76,7 @@ Returns: `1` if equal, `0` otherwise.
 
 ### `checks.matches(pattern, options?)`
 
-Scores 1 if the output matches the given regular expression.
+Scores 1 if the output matches the regular expression.
 
 ```typescript
 checks.matches(/\d+°[FC]/)
@@ -137,7 +137,7 @@ Returns: `1` if the tool wasn't called, `0` otherwise.
 
 ### `checks.toolOrder(expectedOrder)`
 
-Scores 1 if the tools were called in the specified order. Uses relaxed matching — other tool calls between the expected tools are allowed.
+Scores 1 if the tools were called in the specified order. Uses relaxed matching. Other tool calls between the expected tools are allowed.
 
 ```typescript
 checks.toolOrder(['search', 'summarize', 'respond'])

package/.docs/reference/evals/completeness.md

@@ -40,7 +40,7 @@ The scorer extracts and analyzes several types of elements:
 - Nouns: Key objects, concepts, and entities
 - Verbs: Actions and states (converted to infinitive form)
 - Topics: Main subjects and themes
-- Terms: Individual significant words
+- Terms: Individual substantial words
 
 The extraction process includes:
 
@@ -83,10 +83,10 @@ Final score: `(covered_elements / total_input_elements) * scale`
 
 A completeness score between 0 and 1:
 
-- **1.0**: Thoroughly addresses all aspects of the query with comprehensive detail.
-- **0.7–0.9**: Covers most important aspects with good detail, minor gaps.
-- **0.4–0.6**: Addresses some key points but missing important aspects or lacking detail.
-- **0.1–0.3**: Only partially addresses the query with significant gaps.
+- **1.0**: Thoroughly addresses all aspects of the query with detailed detail.
+- **0.7 to 0.9**: Covers most important aspects with good detail, minor gaps.
+- **0.4 to 0.6**: Addresses some key points but missing important aspects or lacking detail.
+- **0.1 to 0.3**: Only partially addresses the query with substantial gaps.
 - **0.0**: Fails to address the query or provides irrelevant information.
 
 ## Example

package/.docs/reference/evals/content-similarity.md

@@ -89,11 +89,11 @@ To add this scorer to an agent, see the [Scorers overview](https://mastra.ai/doc
 
 A similarity score between 0 and 1:
 
-- **1.0**: Perfect match – content is nearly identical.
-- **0.7–0.9**: High similarity – minor differences in word choice or structure.
-- **0.4–0.6**: Moderate similarity – general overlap with noticeable variation.
-- **0.1–0.3**: Low similarity – few common elements or shared meaning.
-- **0.0**: No similarity – completely different content.
+- **1.0**: Perfect match, content is nearly identical.
+- **0.7 to 0.9**: High similarity, minor differences in word choice or structure.
+- **0.4 to 0.6**: Moderate similarity, general overlap with noticeable variation.
+- **0.1 to 0.3**: Low similarity, few common elements or shared meaning.
+- **0.0**: No similarity, completely different content.
 
 ## Related
 

package/.docs/reference/evals/context-precision.md

@@ -28,7 +28,7 @@ Use when optimizing context selection for:
 
 **options** (`ContextPrecisionMetricOptions`): Configuration options for the scorer
 
-**Note**: Either `context` or `contextExtractor` must be provided. If both are provided, `contextExtractor` takes precedence.
+Either `context` or `contextExtractor` must be provided. If both are provided, `contextExtractor` takes precedence.
 
 ## `.run()` returns
 
@@ -85,7 +85,7 @@ Use results to:
 
 ### Example Calculation
 
-Given context: `[relevant, irrelevant, relevant, irrelevant]`
+context: `[relevant, irrelevant, relevant, irrelevant]`
 
 - Position 0: Relevant → Precision = 1/1 = 1.0
 - Position 1: Skip (irrelevant)

package/.docs/reference/evals/context-recall.md

@@ -4,7 +4,7 @@
 
 The `createContextRecallScorer()` function creates a scorer that evaluates how well retrieved context covers the claims in a ground-truth reference answer. It measures retrieval completeness by checking what fraction of the ground truth's claims are attributable to the retrieved context.
 
-This scorer requires a ground-truth reference answer, making it suitable for labeled datasets in CI or test environments. When `groundTruth` is not provided in the run, the scorer returns a score of 0 rather than throwing an error.
+This scorer requires a ground-truth reference answer, making it suitable for labeled datasets in CI or test environments. When `groundTruth` isn't provided in the run, the scorer returns a score of 0 rather than throwing an error.
 
 ## RAG retrieval evaluation
 
@@ -28,7 +28,7 @@ Use when running evaluations against curated test sets:
 
 **options** (`ContextRecallMetricOptions`): Configuration options for the scorer
 
-**Note**: Either `context` or `contextExtractor` must be provided. When both are provided, `contextExtractor` is used only if the run input and output are agent-shaped (`MastraDBMessage[]`); otherwise the scorer falls back to `context`.
+Either `context` or `contextExtractor` must be provided. When both are provided, `contextExtractor` is used only if the run input and output are agent-shaped (`MastraDBMessage[]`); otherwise the scorer falls back to `context`.
 
 ## `.run()` returns
 
@@ -62,11 +62,11 @@ Where:
 
 These ranges assume the default `scale` of 1. When using a custom scale, multiply accordingly.
 
-- **0.9-1.0**: Excellent recall — context covers nearly all ground-truth claims
-- **0.7-0.8**: Good recall — most claims are covered, minor gaps
-- **0.4-0.6**: Moderate recall — significant information missing from context
-- **0.1-0.3**: Poor recall — most ground-truth claims not found in context
-- **0.0**: No recall — none of the ground-truth claims are in the context
+- **0.9-1.0**: Excellent recall, context covers nearly all ground-truth claims
+- **0.7-0.8**: Good recall. Most claims are covered, with minor gaps
+- **0.4-0.6**: Moderate recall, substantial information missing from context
+- **0.1-0.3**: Poor recall, most ground-truth claims not found in context
+- **0.0**: No recall, none of the ground-truth claims are in the context
 
 ### Reason analysis
 
@@ -87,7 +87,7 @@ Use results to:
 
 ### Example calculation
 
-Given ground truth: "Einstein was born in 1879. He developed relativity. He won the Nobel Prize."
+ground truth: "Einstein was born in 1879. He developed relativity. He won the Nobel Prize."
 
 Claims extracted: 3
 

package/.docs/reference/evals/context-relevance.md

@@ -11,7 +11,7 @@ It's especially useful for these use cases:
 Best for evaluating context quality in:
 
 - Chat systems where context usage matters
-- RAG pipelines needing nuanced relevance assessment
+- RAG pipelines needing detailed relevance assessment
 - Systems where missing context affects quality
 
 ## Context selection optimization
@@ -40,7 +40,7 @@ Note: Either `context` or `contextExtractor` must be provided. If both are provi
 
 ### Weighted Relevance Scoring
 
-Context Relevance uses a sophisticated scoring algorithm that considers:
+Context Relevance uses a advanced scoring algorithm that considers:
 
 1. **Relevance Levels**: Each context piece is classified with weighted values:
 
@@ -77,7 +77,7 @@ Final Score = max(0, Base Score - Usage Penalty - Missing Penalty) × scale
 
 - **0.9-1.0**: Excellent - all context highly relevant and used
 - **0.7-0.8**: Good - mostly relevant with minor gaps
-- **0.4-0.6**: Mixed - significant irrelevant or unused context
+- **0.4-0.6**: Mixed - substantial irrelevant or unused context
 - **0.2-0.3**: Poor - mostly irrelevant context
 - **0.0-0.1**: Very poor - no relevant context found
 
@@ -428,7 +428,7 @@ console.log(result)
 
 ### Dynamic context extraction
 
-Extract context dynamically based on the run input:
+Extract context at runtime based on the run input:
 
 ```typescript
 import { createContextRelevanceScorerLLM } from '@mastra/evals'

package/.docs/reference/evals/create-scorer.md

@@ -110,7 +110,7 @@ export const responseQuality = createScorer({
 
 With this configuration, a failed request has at most three provider attempts: the initial request plus two processor retries. If `generateScore` completes and `generateReason` receives a retryable failure, only `generateReason` retries.
 
-`StreamErrorRetryProcessor` honors retryable provider metadata and narrow custom matchers. It keeps `retryUnknownErrors` disabled by default, so authentication, invalid-request, and context-length errors fail immediately unless you explicitly match them. It bounds `Retry-After` values to `30_000` milliseconds by default; use `maxRetryAfterMs` to change that cap.
+`StreamErrorRetryProcessor` honors retryable provider metadata and narrow custom matchers. It keeps `retryUnknownErrors` disabled by default, so authentication, invalid-request, and context-length errors fail immediately unless you explicitly match them. It bounds `Retry-After` values to `30_000` milliseconds by default. Use `maxRetryAfterMs` to change that cap.
 
 Avoid adding outer scorer or workflow retries. Avoid combining a nonzero model retry setting with this processor unless you intentionally accept additional attempts.
 

package/.docs/reference/evals/faithfulness.md

@@ -65,9 +65,9 @@ Final score: `(supported_claims / total_claims) * scale`
 A faithfulness score between 0 and 1:
 
 - **1.0**: All claims are accurate and directly supported by the context.
-- **0.7–0.9**: Most claims are correct, with minor additions or omissions.
-- **0.4–0.6**: Some claims are supported, but others are unverifiable.
-- **0.1–0.3**: Most of the content is inaccurate or unsupported.
+- **0.7 to 0.9**: Most claims are correct, with minor additions or omissions.
+- **0.4 to 0.6**: Some claims are supported, but others are unverifiable.
+- **0.1 to 0.3**: Most of the content is inaccurate or unsupported.
 - **0.0**: All claims are false or contradict the context.
 
 ## Example

package/.docs/reference/evals/filter-run.md

@@ -2,7 +2,7 @@
 
 # filterRun()
 
-Creates a `prepareRun` function from declarative options. Pass the result to `createScorer()` to filter messages, limit context size, and drop unnecessary fields before the scorer pipeline runs.
+Creates a `prepareRun` function from declarative options. Pass the result to `createScorer()` to filter messages and limit context size. It also drops unnecessary fields before the scorer pipeline runs.
 
 Use [`filterRun()`](#usage-example) for declarative filtering. Write a custom `prepareRun` function directly when you need imperative logic that `filterRun()` doesn't cover. See [Custom scorers: input filtering](https://mastra.ai/docs/evals/custom-scorers) for more.
 
@@ -88,7 +88,7 @@ const simpleScorer = createScorer({
 
 **options.dropGroundTruth** (`boolean`): Remove ground truth from the run.
 
-**Returns:** `(run: ScorerRun) => ScorerRun` — A function suitable for the `prepareRun` option on [`createScorer()`](https://mastra.ai/reference/evals/create-scorer).
+**Returns:** `(run: ScorerRun) => ScorerRun`. A function suitable for the `prepareRun` option on [`createScorer()`](https://mastra.ai/reference/evals/create-scorer).
 
 ## Part types
 

package/.docs/reference/evals/hallucination.md

@@ -88,13 +88,13 @@ Final score: `(hallucinated_statements / total_statements) * scale`
 
 A hallucination score between 0 and 1:
 
-- **0.0**: No hallucination — all claims match the context.
-- **0.3–0.4**: Low hallucination — a few contradictions.
-- **0.5–0.6**: Mixed hallucination — several contradictions.
-- **0.7–0.8**: High hallucination — many contradictions.
-- **0.9–1.0**: Complete hallucination — most or all claims contradict the context.
+- **0.0**: No hallucination, all claims match the context.
+- **0.3 to 0.4**: Low hallucination, a few contradictions.
+- **0.5 to 0.6**: Mixed hallucination, several contradictions.
+- **0.7 to 0.8**: High hallucination, many contradictions.
+- **0.9 to 1.0**: Complete hallucination, most or all claims contradict the context.
 
-**Note:** The score represents the degree of hallucination - lower scores indicate better factual alignment with the provided context
+The score represents the degree of hallucination - lower scores indicate better factual alignment with the provided context
 
 ## Examples
 

package/.docs/reference/evals/keyword-coverage.md

@@ -66,11 +66,11 @@ Final score: `(matched_keywords / total_keywords) * scale`
 
 A coverage score between 0 and 1:
 
-- **1.0**: Complete coverage – all keywords present.
-- **0.7–0.9**: High coverage – most keywords included.
-- **0.4–0.6**: Partial coverage – some keywords present.
-- **0.1–0.3**: Low coverage – few keywords matched.
-- **0.0**: No coverage – no keywords found.
+- **1.0**: Complete coverage, all keywords present.
+- **0.7 to 0.9**: High coverage, most keywords included.
+- **0.4 to 0.6**: Partial coverage, some keywords present.
+- **0.1 to 0.3**: Low coverage, few keywords matched.
+- **0.0**: The response contains none of the keywords.
 
 ### Special Cases
 
@@ -80,7 +80,7 @@ The scorer handles several special cases:
 - Single word: Treated as a single keyword
 - Technical terms: Preserves compound technical terms (e.g., "React.js", "machine learning")
 - Case differences: "JavaScript" matches "javascript"
-- Common words: Ignored in scoring to focus on meaningful keywords
+- Common words: Ignored in scoring to focus on useful keywords
 
 ## Example
 

package/.docs/reference/evals/mastra-scorer.md

@@ -4,7 +4,7 @@
 
 The `MastraScorer` class is the base class for all scorers in Mastra. It provides a standard `.run()` method for evaluating input/output pairs and supports multi-step scoring workflows with preprocess → analyze → generateScore → generateReason execution flow.
 
-**Note:** Most users should use [`createScorer`](https://mastra.ai/reference/evals/create-scorer) to create scorer instances. Direct instantiation of `MastraScorer` isn't recommended.
+Most users should use [`createScorer`](https://mastra.ai/reference/evals/create-scorer) to create scorer instances. Direct instantiation of `MastraScorer` isn't recommended.
 
 ## How to get a `MastraScorer` instance
 
@@ -26,7 +26,7 @@ const scorer = createScorer({
 
 ## `.run()` method
 
-The `.run()` method is the primary way to execute your scorer and evaluate input/output pairs. It processes the data through your defined steps (preprocess → analyze → generateScore → generateReason) and returns a comprehensive result object with the score, reasoning, and intermediate results.
+The `.run()` method is the primary way to execute your scorer and evaluate input/output pairs. It processes the data through your defined steps (preprocess → analyze → generateScore → generateReason) and returns a detailed result object with the score, reasoning, and intermediate results.
 
 ```typescript
 const result = await scorer.run({

package/.docs/reference/evals/noise-sensitivity.md

@@ -2,9 +2,9 @@
 
 # Noise sensitivity scorer
 
-The `createNoiseSensitivityScorerLLM()` function creates a **CI/testing scorer** that evaluates how robust an agent is when exposed to irrelevant, distracting, or misleading information. Unlike live scorers that evaluate single production runs, this scorer requires predetermined test data including both baseline responses and noisy variations.
+The `createNoiseSensitivityScorerLLM()` function creates a **CI/testing scorer** that evaluates how reliable an agent is when exposed to irrelevant, distracting, or misleading information. Unlike live scorers that evaluate single production runs, this scorer requires predetermined test data including both baseline responses and noisy variations.
 
-**Important:** This isn't a live scorer. It requires pre-computed baseline responses and can't be used for real-time agent evaluation. Use this scorer in your CI/CD pipeline or testing suites only.
+This isn't a live scorer. It requires pre-computed baseline responses and can't be used for real-time agent evaluation. Use this scorer in your CI/CD pipeline or testing suites only.
 
 Before using the noise sensitivity scorer, prepare your test data:
 
@@ -177,7 +177,7 @@ Include in your test harness to:
 
 - Benchmark different models' noise resistance before deployment
 - Identify agents vulnerable to manipulation during development
-- Create comprehensive test coverage for various noise types
+- Create detailed test coverage for various noise types
 - Ensure consistent behavior across updates
 
 ### Security Testing
@@ -194,7 +194,7 @@ Evaluate resistance in controlled environments:
 - **1.0**: Perfect robustness - no impact detected
 - **0.8-0.9**: Excellent - minimal impact, core functionality preserved
 - **0.6-0.7**: Good - some impact but acceptable for most use cases
-- **0.4-0.5**: Concerning - significant vulnerabilities detected
+- **0.4-0.5**: Concerning - substantial vulnerabilities detected
 - **0.0-0.3**: Critical - agent severely compromised by noise
 
 ### Dimension analysis
@@ -472,7 +472,7 @@ const strictScorer = createNoiseSensitivityScorerLLM({
 
 ## CI test suite: Testing different noise types
 
-Create comprehensive test suites to evaluate agent performance across various noise categories in your CI pipeline:
+Create detailed test suites to evaluate agent performance across noise categories in your CI pipeline:
 
 ```typescript
 import { createNoiseSensitivityScorerLLM } from '@mastra/evals'