Skip to main content
Glama
Sign In
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Join Group

join_group

Add the user to a Fulcra group by ID at their explicit request, enabling group shares and any listed read-only data types until they leave.

Instructions

Join a Fulcra group on the user's behalf, at their explicit request.

Members can receive shares made to the group. If the group lists data types (see get_groups), joining also shares those read-only with its owner until the user leaves (see leave_group). Show the user the group's details first. Anyone who knows a group's ID can join it.

Input Schema

NameRequiredDescriptionDefault
group_idYesThe group to join, from `get_groups`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.7
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations, it discloses important behavior: members can receive group shares, joining may share listed data types read-only with the owner until the user leaves, and anyone with the group ID can join. This is exactly the kind of contextual risk and permission information an agent needs.

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 front-loaded with the action and then adds necessary caveats and prerequisites. It is slightly longer than minimal but every sentence provides useful context.

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?

For a one-parameter mutation with no output schema, the description covers the prerequisite user request, the required display of group details, the sharing consequences, and the related leave_group action. Nothing essential is missing.

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 coverage is 100%, so the single group_id parameter is already well documented in the schema. The description reinforces that the ID should come from get_groups, but adds no new syntax or format 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 uses a specific verb and resource: "Join a Fulcra group." It also distinguishes this action from sibling tools by referencing get_groups for details and leave_group for undoing membership.

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?

It gives explicit usage conditions: join only on the user's behalf and at their explicit request, and show the user the group's details first. It also explains the consequence of joining when the group lists data types.

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