Skip to main content
Glama
Sign In
Fulcra MCP Server

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Standing Open Invitation

prepare_standing_agent_invitation
Destructive

Retrieves the user's standing open invitation, creating it on first use, and optionally saves an inviter name while keeping responder outboxes separate.

Instructions

Get the user's standing open invitation (created on first use; no template grants added). Responders get separate outboxes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_standing_agent_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviter_nameNoName to save for the invitation text; "" clears it, omit to keep.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.7

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description's lead verb 'Get' implies a read operation, creating a mismatch even though 'created on first use' partially discloses writes. The destructive aspect is never explained (what is overwritten, whether re-invocation resets state), and phrases like 'no template grants added' and 'separate outboxes' are opaque.

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?

It is brief and front-loads the core resource, with the parenthetical carrying behavioral caveats. Some phrasing ('no template grants added', 'Responders get separate outboxes') is dense and unclear, costing a little clarity but not length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 schema coverage, the description need not detail return values, and it does communicate creation and outbox behavior. However, it leaves the mutation/destructive nature and sibling disambiguation unresolved, which are important for correct selection and safe invocation.

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 single inviter_name parameter is fully documented in the schema, including the 'omit to keep' / '"" clears it' semantics. The description adds nothing beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource (a standing open invitation) and adds creation semantics, but its verb 'Get' conflicts with both the tool name ('prepare') and the annotations, and it does not differentiate from siblings like prepare_agent_invitation or create_agent_invitation. An agent cannot easily tell when this differs from those siblings.

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 when-to-use guidance and no mention of alternatives among the many invitation-related siblings. The parenthetical describes behavior ('created on first use') but not the conditions that should lead an agent to select this tool over prepare_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