Skip to main content
Glama
Sign In

OpenMandate

by ai.openmandate
OverviewDiscussionsAdmin

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "want": "<want>",
      "offer": "<offer>"
    },
    "name": "openmandate_create_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
wantYesWhat the user is looking for (cofounder, service provider, investor, etc.). Minimum 20 characters.
offerYesWhat the user brings to the table (skills, experience, resources, etc.). Minimum 20 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses meaningful behaviors: verified contacts are automatically attached, the response includes follow-up questions, and the tool requires the user to have verified contacts. No contradiction with annotations exists.

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 compact yet complete: purpose, required inputs, automatic side effect, return behavior, mandatory next step, and prerequisite handling are each covered in a single sentence or short paragraph. Every sentence earns its place with no 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?

With no output schema, the description still explains what the tool returns (mandate with follow-up questions). It also covers preconditions, side effects, and the required follow-up action, giving an agent everything needed to invoke this tool correctly within the surrounding workflow.

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 fully documents both parameters, including the 20-character minimum. The description lightly reinforces that 'want' is what the user seeks and 'offer' is what they bring, but adds no material semantic detail beyond the schema.

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 ('Create a new mandate on OpenMandate') and immediately explains the two inputs (want and offer). This clearly distinguishes the tool from sibling operations like openmandate_close_mandate, openmandate_get_mandate, and openmandate_submit_answers.

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 workflow guidance: if no verified contacts exist, the user must add one or use openmandate_list_contacts to check, and the agent must relay follow-up questions and collect real answers before calling openmandate_submit_answers. It also includes a when-not instruction ('Do not answer questions on the user's behalf').

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

All OpenMandate toolsInspect
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