OpenMandate

openmandate_create_mandate

Create a new mandate on OpenMandate. Provide what the user is looking for (want) and what they bring to the table (offer). The user's verified contacts are automatically attached.

Returns the mandate with follow-up questions. You MUST relay these questions to the user and collect their actual answers before calling openmandate_submit_answers. Do not answer questions on the user's behalf.

If the user has no verified contacts, they must add one first at https://openmandate.ai/settings or use openmandate_list_contacts to check.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`want`	Yes	What the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters.
`offer`	Yes	What the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters.

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint=false and destructiveHint=false annotations, the description discloses that verified contacts are automatically attached, that the tool returns follow-up questions, and that the agent must not answer on the user's behalf. It also alerts about the no-contacts case.

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 description is structured into three focused paragraphs, front-loading the main action. While slightly longer than minimal, every sentence adds critical information about follow-up questions, contact requirements, and safety.

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?

Given the simple two-parameter schema and no output schema, the description provides necessary context by stating the return type (mandate with follow-up questions) and the prerequisite condition regarding verified contacts. This is complete enough for an agent to use the tool correctly.

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?

The schema already provides complete descriptions for both 'want' and 'offer' with 100% coverage. The description adds only a colloquial restatement ('what the user is looking for' and 'what they bring to the table'), which does not significantly enhance the schema's meaning.

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 clearly states 'Create a new mandate on OpenMandate' with a specific verb and resource. It explains the two key inputs and distinguishes this creation tool from siblings like openmandate_submit_answers or openmandate_list_mandates.

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 explicitly instructs the agent to relay follow-up questions and collect answers before calling openmandate_submit_answers, and provides a prerequisite step: if no verified contacts, use openmandate_list_contacts or add one via settings. This gives clear when-to-use and next-step guidance.

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

All OpenMandate tools Inspect

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

A4.4/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Tools are well-defined around specific actions on contacts, mandates, and matches, such as openmandate_add_contact vs. openmandate_update_contact or openmandate_create_mandate vs. openmandate_close_mandate. The descriptions reinforce unique roles, preventing misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with the 'openmandate_' prefix, such as openmandate_add_contact, openmandate_list_matches, and openmandate_verify_contact. This uniformity makes the set predictable and easy to navigate, with no deviations in naming conventions.

Tool Count5/5

With 15 tools, the count is well-scoped for managing contacts, mandates, and matches on OpenMandate. Each tool earns its place by covering essential operations like CRUD for contacts, mandate lifecycle management, and match interactions, without feeling excessive or insufficient for the domain.

Completeness5/5

The tool set provides complete coverage for the OpenMandate domain, including full CRUD for contacts, mandate creation to closure, match handling, and outcome reporting. There are no obvious gaps; tools support the entire workflow from contact verification to match resolution, ensuring agents can operate without dead ends.

Resources

Need Help?