A
licenseNot graded
qualityD
maintenanceMulti-agent sales email generation server that creates, evaluates, and sends personalized sales emails via SendGrid, using AI to craft diverse email styles and select the best one.
MIT
Universal Agents
Server Details
Ask Universal Agents what we sell (Interplay), pricing, and FAQs; draft an intro email.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 16 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.7/5.0
Scored across 4 tools
Disambiguation4/5
The four tools mostly have distinct roles: overview, FAQ, pricing, and intro drafting. There is some potential overlap between about_universal_agents and answer_faq, since both can address who the company is for and what it offers, but the descriptions provide enough separation for an agent to choose correctly.
Naming Consistency4/5
The names are consistently snake_case and mostly follow a verb_noun pattern: answer_faq, get_pricing, request_intro. About_universal_agents is more descriptive than action-oriented, but it is still readable and does not break the overall convention.
Tool Count5/5
Four tools is well-scoped for a company information and outreach server. Each tool covers a clear need without redundancy or unnecessary surface area.
Completeness4/5
The server covers the core informational needs: company overview, FAQ, pricing, and a way to initiate contact. Minor gaps exist, such as scheduling or direct contact details, but request_intro provides a workable path for the primary user journey.
Available Tools
4 toolsabout_universal_agentsAbout Universal AgentsBRead-onlyInspect
What Universal Agents sells (Interplay: the brain, the playbook, Living Blocks, the universal agent), how an engagement starts, and who it is for.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| source | Yes | |
| summary | Yes | |
| agent_may | Yes | What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off. |
| provenance | Yes | |
| what_we_sell | Yes | |
| how_it_starts | Yes | |
| who_it_is_for | Yes |
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds scope context (the content areas it covers), but for an informational tool it doesn't need to say much more; return format is handled by the output schema.
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?
One front-loaded sentence that carries the full content scope with no filler. The parenthetical list is dense but useful, not padding.
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 no-param, read-only overview tool with an output schema, the description covers what an agent needs to decide and call. Only the omission of explicit sibling routing keeps it from being complete.
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?
Zero parameters, so the baseline is 4. The description correctly indicates no input is required, and there is nothing in the schema for it to compensate for.
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 names the resource (Universal Agents) and enumerates the content covered: what it sells (Interplay, the brain, the playbook, Living Blocks, the universal agent), how an engagement starts, and who it's for. That is concrete and distinguishable from get_pricing or request_intro, though the verb is implicit rather than an explicit 'returns/describes'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance and no routing against siblings. An agent facing answer_faq, get_pricing, and request_intro gets no rule for choosing this overview over them; the only clue is the absence of parameters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
answer_faqAnswer a frequently asked questionARead-onlyInspect
Answers common questions about Universal Agents: agent readiness, working with teams, industries, timeline, what makes us different, data safety, adoption. Omit the question to get all of them.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| question | No | The question or a keyword, e.g. "data" or "how long". |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| match | Yes | all: no question given; best: the closest answers; none: no match, so all of them. |
| answers | Yes | |
| agent_may | Yes | What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off. |
| provenance | Yes |
TDQS
A3.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral trait not in the annotations: omitting the question returns the full set of FAQs, which tells the agent how the default invocation behaves.
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 compact sentences, front-loaded with the topic scope and closing with the omission default. No wasted phrasing, though the topic list is long and could be summarized.
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, return values need not be described, and the topic enumeration plus default behavior give the agent enough to invoke it correctly. Missing only guidance on how it relates to the sibling tools.
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% for the single parameter, and the schema already states that a keyword like 'data' or 'how long' is valid. The description reinforces this by enumerating topics, which is useful for matching, but adds little beyond the schema baseline.
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?
States a clear verb (Answers) and the resource/topic scope (common questions about Universal Agents), enumerating the covered domains. It is distinguishable from siblings like about_universal_agents, though it doesn't explicitly say how it differs.
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?
The only usage guidance is the default behavior: 'Omit the question to get all of them.' There is no explicit when-to-use-this-vs-siblings guidance, such as when to prefer about_universal_agents or get_pricing over the FAQ.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_pricingGet pricingBRead-onlyInspect
Universal Agents pricing: the paid pilot, the cost to continue rollout, and licensing and support.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| pricing | Yes | |
| agent_may | Yes | What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off. |
| provenance | Yes |
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read operation. The description adds no behavioral traits beyond that—no authentication, rate limits, or caching info. Since annotations carry the safety profile and the tool is parameterless, a 3 is appropriate as the description adds nothing but also contradicts nothing.
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?
The single sentence is front-loaded and efficient, listing the three key pricing areas. It avoids waste, though it is a fragment (no verb) and could be slightly more structured. It earns its place by summarizing the scope.
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?
Given no parameters, an output schema, and simple annotations, the description provides the necessary scope (what pricing information is returned). The output schema presumably details return values, so the description need not explain them. It is complete enough for an agent to invoke, though it lacks sibling differentiation.
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?
With zero parameters, the baseline is 4. The description does not need to explain parameters, and it correctly omits any. No penalty 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?
The description states a specific resource (Universal Agents pricing) and enumerates the sub-topics covered: paid pilot, cost to continue rollout, and licensing and support. It is a clear retrieval tool, though it doesn't explicitly differentiate itself from siblings like 'about_universal_agents' or 'answer_faq'. It implies pricing-specific content, which is clear enough to distinguish from a general FAQ, but not as sharply as naming the sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance on when to use this tool versus alternatives like 'about_universal_agents' or 'answer_faq'. A user might ask a general pricing question, and it's not stated whether this tool is the right one or if 'answer_faq' handles pricing. The description implies usage context (pricing queries) but leaves the agent to infer when this is preferable to siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
request_introRequest an intro callARead-onlyInspect
Drafts an intro email to Universal Agents for the person you are helping, with a mailto link they can send. Sends nothing itself.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | What they want AI to change. | |
| name | No | Their name. | |
| size | No | Roughly how many people. | |
| agency | No | Their agency. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| to | Yes | |
| body | Yes | |
| sent | Yes | |
| mailto | Yes | |
| subject | Yes | |
| agent_may | Yes | What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off. |
| provenance | Yes |
TDQS
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'Sends nothing itself' plus the fact that the output is a mailto link the user sends. That is useful side-effect disclosure beyond the annotations, though it says nothing about permissions or data handling.
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, front-loaded sentences with zero filler; the action comes first and the no-side-effect caveat second.
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 param coverage, the description only needs to establish purpose and side-effect behavior, which it does. The one remaining gap is explicit routing guidance against the sibling informational tools.
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 the schema already documents goal, name, size, and agency. The description adds only the framing that the draft is for 'the person you are helping', which is marginal context rather than new parameter meaning.
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 names a specific verb and artifact ('Drafts an intro email to Universal Agents') and adds the concrete output ('with a mailto link they can send'), so an agent knows exactly what the tool produces. It doesn't explicitly differentiate against the siblings (about_universal_agents, answer_faq, get_pricing), but the action is self-evidently distinct.
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 only implied via 'for the person you are helping', which hints at the context without stating when to reach for this tool versus answering a FAQ or pricing question. No explicit when-not or prerequisite guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
4 tool updates
- Changed
about_universal_agents1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": false, + "properties": { + "agent_may": { + "additionalProperties": false, + "description": "What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.", + "properties": { + "label": { + "type": "string" + }, + "level": { + "type": "integer" + }, + "note": { + "type": "string" + } + }, + "required": [ + "level", + "label", + "note" + ], + "type": "object" + }, + "how_it_starts": { + "type": "string" + }, + "provenance": { + "additionalProperties": false, + "properties": { + "accountable": { + "additionalProperties": false, + "properties": { + "contact": { + "type": "string" + }, + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title", + "contact" + ], + "type": "object" + }, + "answer_type": { + "enum": [ + "product" + ], + "type": "string" + }, + "authors": { + "items": { + "additionalProperties": false, + "properties": { + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title" + ], + "type": "object" + }, + "type": "array" + }, + "effective": { + "type": "string" + }, + "source": { + "additionalProperties": false, + "properties": { + "path": { + "type": "string" + }, + "repo": { + "type": "string" + } + }, + "required": [ + "repo", + "path" + ], + "type": "object" + } + }, + "required": [ + "answer_type", + "authors", + "accountable", + "source", + "effective" + ], + "type": "object" + }, + "source": { + "type": "string" + }, + "summary": { + "type": "string" + }, + "what_we_sell": { + "type": "string" + }, + "who_it_is_for": { + "type": "string" + } + }, + "required": [ + "summary", + "what_we_sell", + "how_it_starts", + "who_it_is_for", + "source", + "provenance", + "agent_may" + ], + "type": "object" +}
- Changed
answer_faq1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": false, + "properties": { + "agent_may": { + "additionalProperties": false, + "description": "What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.", + "properties": { + "label": { + "type": "string" + }, + "level": { + "type": "integer" + }, + "note": { + "type": "string" + } + }, + "required": [ + "level", + "label", + "note" + ], + "type": "object" + }, + "answers": { + "items": { + "additionalProperties": false, + "properties": { + "agent_may": { + "additionalProperties": false, + "description": "What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.", + "properties": { + "label": { + "type": "string" + }, + "level": { + "type": "integer" + }, + "note": { + "type": "string" + } + }, + "required": [ + "level", + "label", + "note" + ], + "type": "object" + }, + "answer": { + "type": "string" + }, + "provenance": { + "additionalProperties": false, + "properties": { + "accountable": { + "additionalProperties": false, + "properties": { + "contact": { + "type": "string" + }, + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title", + "contact" + ], + "type": "object" + }, + "answer_type": { + "enum": [ + "pricing", + "product" + ], + "type": "string" + }, + "authors": { + "items": { + "additionalProperties": false, + "properties": { + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title" + ], + "type": "object" + }, + "type": "array" + }, + "effective": { + "type": "string" + }, + "source": { + "additionalProperties": false, + "properties": { + "path": { + "type": "string" + }, + "repo": { + "type": "string" + } + }, + "required": [ + "repo", + "path" + ], + "type": "object" + } + }, + "required": [ + "answer_type", + "authors", + "accountable", + "source", + "effective" + ], + "type": "object" + }, + "question": { + "type": "string" + } + }, + "required": [ + "question", + "answer", + "provenance", + "agent_may" + ], + "type": "object" + }, + "type": "array" + }, + "match": { + "description": "all: no question given; best: the closest answers; none: no match, so all of them.", + "enum": [ + "all", + "best", + "none" + ], + "type": "string" + }, + "provenance": { + "additionalProperties": false, + "properties": { + "accountable": { + "additionalProperties": false, + "properties": { + "contact": { + "type": "string" + }, + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title", + "contact" + ], + "type": "object" + }, + "answer_type": { + "enum": [ + "pricing", + "product" + ], + "type": "string" + }, + "authors": { + "items": { + "additionalProperties": false, + "properties": { + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title" + ], + "type": "object" + }, + "type": "array" + }, + "effective": { + "type": "string" + }, + "source": { + "additionalProperties": false, + "properties": { + "path": { + "type": "string" + }, + "repo": { + "type": "string" + } + }, + "required": [ + "repo", + "path" + ], + "type": "object" + } + }, + "required": [ + "answer_type", + "authors", + "accountable", + "source", + "effective" + ], + "type": "object" + } + }, + "required": [ + "match", + "answers", + "provenance", + "agent_may" + ], + "type": "object" +}
- Changed
get_pricing1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": false, + "properties": { + "agent_may": { + "additionalProperties": false, + "description": "What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.", + "properties": { + "label": { + "type": "string" + }, + "level": { + "type": "integer" + }, + "note": { + "type": "string" + } + }, + "required": [ + "level", + "label", + "note" + ], + "type": "object" + }, + "pricing": { + "type": "string" + }, + "provenance": { + "additionalProperties": false, + "properties": { + "accountable": { + "additionalProperties": false, + "properties": { + "contact": { + "type": "string" + }, + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title", + "contact" + ], + "type": "object" + }, + "answer_type": { + "enum": [ + "pricing" + ], + "type": "string" + }, + "authors": { + "items": { + "additionalProperties": false, + "properties": { + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title" + ], + "type": "object" + }, + "type": "array" + }, + "effective": { + "type": "string" + }, + "source": { + "additionalProperties": false, + "properties": { + "path": { + "type": "string" + }, + "repo": { + "type": "string" + } + }, + "required": [ + "repo", + "path" + ], + "type": "object" + } + }, + "required": [ + "answer_type", + "authors", + "accountable", + "source", + "effective" + ], + "type": "object" + } + }, + "required": [ + "pricing", + "provenance", + "agent_may" + ], + "type": "object" +}
- Changed
request_intro1 field changed- changed
Output schema / (root)Previous value: -nullNew value: +{ + "additionalProperties": false, + "properties": { + "agent_may": { + "additionalProperties": false, + "description": "What an agent may do with this answer unsupervised: a level on the Universal Agents Delegation Map, 1 Tell to 7 Hands Off.", + "properties": { + "label": { + "type": "string" + }, + "level": { + "type": "integer" + }, + "note": { + "type": "string" + } + }, + "required": [ + "level", + "label", + "note" + ], + "type": "object" + }, + "body": { + "type": "string" + }, + "mailto": { + "type": "string" + }, + "provenance": { + "additionalProperties": false, + "properties": { + "accountable": { + "additionalProperties": false, + "properties": { + "contact": { + "type": "string" + }, + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title", + "contact" + ], + "type": "object" + }, + "answer_type": { + "enum": [ + "code" + ], + "type": "string" + }, + "authors": { + "items": { + "additionalProperties": false, + "properties": { + "name": { + "type": "string" + }, + "title": { + "type": "string" + } + }, + "required": [ + "name", + "title" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "answer_type", + "authors", + "accountable" + ], + "type": "object" + }, + "sent": { + "const": false, + "type": "boolean" + }, + "subject": { + "type": "string" + }, + "to": { + "type": "string" + } + }, + "required": [ + "sent", + "to", + "subject", + "body", + "mailto", + "provenance", + "agent_may" + ], + "type": "object" +}
4 tool updates
- First observed
about_universal_agents - First observed
answer_faq - First observed
get_pricing - First observed
request_intro
Related MCP Connectors
Who the audience is when your customers are agents, and how to be found by them.
Unified book, desk, calendar, prices, and rates for agents. Sign up, pay, pull.
Agent-native marketing email: draft, edit, screenshot, and send from your verified domain.
Agent Interviews is an AI-powered research platform designed to conduct qualitative interviews an...
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceUniq generates personalized emails, HTML pitch pages, and hosted proposal pages in the prospect's branding from seller and prospect URLs. It provides MCP tools for agents to create, retrieve, and track proposals.1AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to draft evidence-grounded cold-email openers, A/B variants, personalized LinkedIn DMs, and SEO content-gap plans for sales and marketing outreach.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to find leads, read buying signals, write and send email and LinkedIn outreach, handle replies, and report results, with built-in safety gates, approvals, limits, and compliance controls.5Apache 2.0
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.