Scribe Mail

List smart fields

list_smart_fields

Read-onlyIdempotent

List the workspace's smart-field definitions — the merge fields available to signature templates (e.g. first name, job position, custom fields). Each carries its kind, whether it's a default field, and an integration_id when its values are synced. The computed Email field is not exposed. Paginated (page/limit).

Input Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`limit`	No	Page size, 1–100 (default 50).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`max_pages`	No	Page cap when auto_paginate is true (default 5).
`auto_paginate`	No	Fetch multiple pages up to `max_pages` (default false).

Output Schema

Name	Required	Description
`data`	Yes
`truncated`	Yes	True when auto_paginate stopped at max_pages with more results remaining.
`pagination`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026
- removedOutput schema / properties / data / items / properties / integration_attribute / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / integration_attribute / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / integration_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / integration_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / slug / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / slug / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 16, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds substantive context beyond that: each item carries `kind`, a `default` flag, and an `integration_id` when synced, plus the notable exclusion that the computed Email field is not exposed — exactly the kind of scope caveat an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the identity of the resource, followed by the useful exclusions. The trailing "Paginated (page/limit)" is redundant with a 100%-covered schema, a minor wasted clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full schema coverage, the description only needs to frame scope and semantics, which it does well (what a smart field is, what fields come back, what is excluded). It stops short of noting auto_paginate's role or any ordering of results, but nothing critical to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so page, limit, auto_paginate and max_pages are already fully documented, and the description's "Paginated (page/limit)" merely repeats that. No added meaning about parameter behavior is provided, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the workspace's smart-field definitions") and immediately glosses the concept as "the merge fields available to signature templates," which an agent can act on without opening the schema. It is clearly distinguishable from the create/update/delete_smart_field siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — an agent would call this to discover available merge fields before creating or previewing a signature — but the description never states when to use this versus alternatives such as create_smart_field or the integration listing tools. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scribe Mail tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.