Vendo AI

Signal Learning insights

sdr_learning_insights

Read-only. Learned weight per signal type and conversion from real outreach outcomes, for one search or per search across the workspace.

Input Schema

Name	Required	Description	Default
`search_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / search_id
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```
First observedJul 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It states read-only and identifies real outreach outcomes as the data source, but it omits permissions, freshness/recompute relationship, and return behavior.

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?

Two short sentences, front-loaded with read-only and then purpose/scope. There is no redundant restatement of the title or tool name.

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?

For a low-complexity read-only analytics endpoint with one optional parameter and no output schema, the description covers safety, data source, and scope. It could clarify return granularity or relationship to recompute, but it is sufficient for correct invocation.

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

Parameters4/5

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

The sole optional search_id has 0% schema description coverage. The description compensates by explaining that including it scopes results to one search while omitting it returns workspace-wide results, adding meaningful semantics beyond the schema.

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

Purpose4/5

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

The description specifies the retrieved artifact: learned weight per signal type and conversion from real outreach outcomes, plus scope for one search or the workspace. It is clear, though it does not explicitly differentiate itself from nearby tools such as sdr_signal_stats or sdr_learning_recompute.

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?

It explains the search_id-based mode, single search versus workspace-wide, which gives useful usage context. However, it provides no explicit when-to-use/when-not guidance or alternative tool routing.

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

All Vendo AI 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?