Skip to main content
Glama

Salesforce

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A4.1/5.0
Behavior4/5

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

Adds context beyond annotations by explaining returned fields, mark_read side effect, and polling behavior. No contradictions with annotations (readOnlyHint, idempotentHint, etc.).

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?

Four concise sentences with front-loaded purpose. Every sentence adds value; no redundant or filler content.

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 read-only, idempotent tool with no output schema, the description covers return fields, filtering, mark_read, and alternative access. Sufficient for agent invocation.

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 coverage is 100% with descriptions. Description reinforces filtering and mark_read use but does not significantly add new meaning. Baseline 3 applies.

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?

Clearly states 'Pull fired events from your subscription feed' and lists returned fields. Differentiates from sibling tools by focusing on recent alerts, but no explicit sibling differentiation.

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

Usage Guidelines4/5

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

Provides guidance on filtering by type and since, how mark_read works, and notes polling suitability. Mentions an alternative REST endpoint. Does not explicitly exclude when not to use.

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

All Salesforce toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

The set mixes Salesforce CRUD tools with a large Pipeworx research and prediction-market platform, and several tools overlap heavily: ask_pipeworx vs ask_pipeworx_beta are functionally identical, grounded/validate_claim/deep_research cover similar lookup/verification territory, and the six polymarket/bet tools share edge-finding purposes with only subtle distinctions. An agent would need to read long descriptions carefully to pick the right one, so misselection risk is high.

Naming Consistency3/5

Salesforce tools follow a clear sf_verb_noun pattern, and the Pipeworx tools mostly use lowercase snake_case phrase names, but the conventions diverge: ask_pipeworx has no underscore, deep_research/entity_profile are noun phrases rather than verb-first, and the sf_* prefix is a separate naming family. It is still readable, but it is not a single predictable pattern.

Tool Count2/5

39 tools is well past the heavy threshold, and most belong to a broad data/research platform rather than the Salesforce scope implied by the server name; only 8 tools are actually Salesforce CRUD/query operations. The count feels bloated for a coherent assistant, even if individual features are useful.

Completeness4/5

The Salesforce subset is complete: create/get/update/delete/query/search/describe/list-object cover the record lifecycle with no dead ends. The broader Pipeworx ecosystem also has strong coverage, including routing, grounded verification, research, entity resolution, memory, and subscriptions, with only minor gaps such as no direct citation-fetch tool and no Salesforce upsert/bulk operations.

Resources