Skip to main content
Glama
Sign In
Fulcra MCP Server

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Prepare Agent Invitation

prepare_agent_invitation

Creates an invitation code and matching response topic so another agent can accept access to a specified Event/ channel. Use it to authorize secure agent-to-agent data sharing.

Instructions

Prepare an invitation code at the user's request; authorizes only its matched return share. Include own_userid/code in the invite. The accepting agent's FIRST message must use the returned topic exactly; never invent codes.

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": {
      "data_type": "<data_type>"
    },
    "name": "prepare_agent_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_typeYesExact owned Event/<uuid> channel without targeted grants.
open_invitationNoReusable invitation with distinct open_invitation topic (not handshake). Never grants access to the template; each responder gets an individual outbox.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.19.1
    • changedInput schema / properties / data_type / description
      Previous value: -"Exact owned, unshared Event/<uuid> channel."New value: +"Exact owned Event/<uuid> channel without targeted grants."
    • changedInput schema / properties / open_invitation / description
      Previous value: -"Reusable invitation with distinct open_invitation topic (not handshake).\nKeeps the template unshared; each authenticated responder gets an individual outbox."New value: +"Reusable invitation with distinct open_invitation topic (not handshake).\nNever grants access to the template; each responder gets an individual outbox."
  2. Addedv1.18.7

TDQS

A3.7/5.0
Behavior4/5

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

Beyond annotations, it discloses important behavioral constraints: the code authorizes only its matched return share, the invite must include own_userid/code, and the accepting agent must use the returned topic exactly. It does not fully explain the lifecycle or misuse consequences, but it adds meaningful operational context.

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 compact and front-loads the purpose before the operational rules. It contains no obvious filler, though the phrase 'Include own_userid/code in the invite' is slightly underspecified.

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 the output schema and full parameter coverage, the description covers the key behavioral constraints an agent needs before calling it. The main remaining gap is sibling differentiation, which keeps it from a 5.

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%, and the schema already explains data_type and open_invitation in detail. The description does not add parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 verb and resource: preparing an invitation code that authorizes a matched return share. It is clear what the tool does, but it does not distinguish this from close siblings such as create_agent_invitation or prepare_standing_agent_invitation.

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 phrase 'at the user's request' gives a general usage context, and the warning 'never invent codes' implies strict handling. However, it does not explicitly say when to choose this tool over create_agent_invitation or prepare_standing_agent_invitation.

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

Deploy Server

Other Tools