Skip to main content
Glama
proxenio

Proxenio MCP Server

Official
by proxenio

Accept Proxenio Introduction

proxenio_accept_match

Accept an incoming introduction request for the principal, creating a deal. Only for matches where the principal is the receiving party.

Instructions

Accept an introduction request on behalf of the human principal.

This creates a deal between the principal and the counterparty. The principal must be the receiving party (user_b) — agents cannot accept introductions that the principal initiated.

IMPORTANT: This is an action with real consequences. It connects two professionals and creates a deal container. Only accept matches that align with the principal's stated intent.

Requires: API key must be set via proxenio_set_api_key first.

Args:

  • match_id (string, UUID): The match ID to accept. Get this from proxenio_get_matches results.

Returns: Confirmation with counterparty details, the new deal ID, and rate limit status.

Guard rails enforced by the API:

  • Principal must be a participant in the match

  • Principal must be the receiving party (user_b), not the requester

  • Match must have an active status

  • An introduction request must exist and be in pending/awaiting_consent state

  • Agent cannot accept the principal's own outgoing requests

Examples:

  • Use when: Principal wants to accept a specific pending introduction

  • Use when: Agent decides a match aligns with principal's intent and should be accepted

  • Don't use when: You haven't checked the match details first (use proxenio_get_matches)

  • Don't use when: The match was initiated by the principal (agent can only accept incoming)

Error Handling:

  • 400: Match not in correct state, no intro request exists

  • 403: Principal is not authorized (e.g., they are the requester, not receiver)

  • 404: Match ID not found

  • 429: Rate limit exceeded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
match_idYesUUID of the match to accept. Get this from proxenio_get_matches. The principal must be the receiving party (user_b), not the requester.
Behavior5/5

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

Annotations only indicate non-read-only and non-destructive, but the description adds critical behavioral context: it creates a deal container, has 'real consequences', connects professionals, and enforces guard rails (principal must be user_b, match must be active, etc.). This goes well beyond the structured annotations and fully informs the agent.

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 lengthy but well-organized into sections (args, returns, guard rails, examples, error handling). It is front-loaded with the core purpose. While every section earns its place, it could be tightened slightly without losing important nuance.

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 there is no output schema, the description appropriately details the return value (confirmation with counterparty details, deal ID, rate limit status). It covers preconditions, API guard rails, and error codes, making it fully complete for an agent to understand the tool's behavior and consequences.

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 schema covers 100% of the parameter and already includes a description. The tool description adds extra value by directing the agent to get the match_id from proxenio_get_matches and reinforcing the user_b constraint, but the schema already conveys the core semantics, so the incremental value is moderate.

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 states a specific verb+resource: 'Accept an introduction request on behalf of the human principal' and explains the resulting action ('creates a deal'). It clearly distinguishes from sibling tools like proxenio_get_matches (fetching) and proxenio_set_api_key (configuration).

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 provides explicit 'Use when' and 'Don't use when' examples, mentions the prerequisite of setting an API key, and points to proxenio_get_matches as the source for match IDs. This gives strong guidance on when to use the tool and when to avoid it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/proxenio/proxenio-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server