Onsa

What to do next

list_next_steps

Read-onlyIdempotent

Returns read-only guidance for what to do next. Without campaignId, it returns the first-search question, active search progress, or campaign names and statuses to choose from. A single accessible campaign is resolved automatically. With campaignId, it returns a ranked to-do list: people who replied, people who accepted an invite but were never messaged, drafts waiting for approval, leads found but never contacted, and setup that is missing. It answers 'what should I do about this campaign today', where get_campaign_stats answers 'how is it doing'. For replies specifically, list_replies is the better source: its awaitingOurReply compares timestamps, while the replied bucket here covers only leads whose sentiment was scored and does not know whether we have since answered. leadIds passed to get_campaign_leads resolves the buckets into named people. Limits of the data: Onsa does not record whether we have already replied, or whether someone was contacted outside Onsa; 'replied' includes only replies whose sentiment was scored, so it is a floor; a withdrawn or unreachable invite leaves no trace, so some 'never contacted' leads may already have been tried. Sentiment is judged once per lead, not per message. Counts are complete; leadIds are capped at 200.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campaignId`	No	Optional campaign to inspect; omitted for workspace guidance

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`items`	Yes
`scope`	No
`total`	No
`returned`	No
`campaigns`	No
`campaignId`	No
`leadsTotal`	No
`nextAction`	No
`campaignUrl`	No
`workspaceUrl`	No
`campaignTitle`	No
`workspaceState`	No
`searchAvailability`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 22, 2026

changedInput schema / properties / campaignId / description

Previous value: -"Campaign to inspect, from list_campaigns or fetch_leads"New value: +"Optional campaign to inspect; omitted for workspace guidance"

removedInput schema / required
```
Removed value: -[
-  "campaignId"
-]
```

addedOutput schema / properties / campaigns

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "campaignUrl": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "leadsTotal": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "status": {
+        "enum": [
+          "search_running",
+          "prospects_available",
+          "no_prospects"
+        ],
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "title",
+      "leadsTotal",
+      "status",
+      "campaignUrl"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / nextAction

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "arguments": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "question": {
+      "type": "string"
+    },
+    "reuseAuthorizedBrief": {
+      "type": "boolean"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / returned

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / scope

Added value: +{
+  "enum": [
+    "workspace",
+    "campaign"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / searchAvailability

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "allowance": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "limit": {
+              "type": "number"
+            },
+            "remaining": {
+              "type": "number"
+            },
+            "used": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "used",
+            "limit",
+            "remaining"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "reason": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "enum": [
+        "available",
+        "blocked",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "reason",
+    "allowance"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / total

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / workspaceState
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / workspaceUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "campaignId",
-  "campaignTitle",
-  "campaignUrl",
-  "leadsTotal",
-  "items"
-]New value: +[
+  "items"
+]

First observedSep 8, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds substantial context beyond that: caveats about the 'replied' bucket being a floor, Onsa not recording whether we replied or whether someone was contacted outside Onsa, withdrawn/unreachable invites leaving no trace, sentiment judged once per lead, counts complete, and leadIds capped at 200. This is exactly the kind of behavioral detail that prevents an agent from over-trusting the data.

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

Conciseness5/5

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

The description is long but each clause earns its place: mode behavior, sibling differentiation, reply-bucket caveat, data limitations, and caps. It is front-loaded with the core purpose before branching into details, and the information is tightly packed without repetition or filler.

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

Completeness5/5

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

For a tool with one optional parameter, an output schema, and annotations already covering safety, the description is complete: it explains both invocation modes, the meaning of returned buckets, how to get more detail, and the known data limits. No gap remains that would prevent an agent from invoking it correctly.

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

Parameters5/5

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

Although schema coverage is 100% for the single optional campaignId, the description adds meaning far beyond the schema: it explains that omitting campaignId returns workspace-level guidance (first-search question, progress, campaign names/statuses) and that a single accessible campaign resolves automatically, while providing campaignId returns a ranked campaign-specific to-do list. This substantially informs parameter choice.

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?

The description opens with a specific verb and resource: 'Returns read-only guidance for what to do next.' It clearly differentiates itself from siblings by stating that get_campaign_stats answers 'how is it doing' and list_replies is better for replies specifically. The two conditional modes (with and without campaignId) are crisply delineated.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: it answers 'what should I do about this campaign today' versus get_campaign_stats for 'how is it doing', and explicitly recommends list_replies for reply-specific needs because its `awaitingOurReply` compares timestamps. It also tells the agent to pass `leadIds` to get_campaign_leads to resolve buckets into named people, which is actionable routing to an alternative.

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

All Onsa 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.

Resources

Need Help?