Skip to main content
Glama
Sign In
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Shares

list_shares
Read-only

List outgoing, incoming, or both data shares to see what you share and what others share with you, including group-sourced entries and your user ID for receiving shares.

Instructions

List what this user shares with others and what others share with them.

Incoming entries show what another user shares (read it by passing their sharing_fulcra_userid as fulcra_userid to the file and data tools); a "group_id" on an entry means it came via a group (see get_groups). Also reports this user's own ID, which others need in order to share with them.

Input Schema

NameRequiredDescriptionDefault
directionNoWhich shares to list: "outgoing", "incoming", or "both".both

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that: the shape of the result (incoming vs outgoing entries), the meaning of `group_id`, and the fact that the user's own ID is returned so others can share with them.

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?

Four short sentences, scope stated first, then interpretation of results. The parenthetical about passing `sharing_fulcra_userid` is dense but earns its place; nothing is padded.

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?

With a single optional parameter, no output schema, and safety covered by annotations, the description carries the needed load by explaining what entries mean and what identifiers come back. A note on ordering or volume of results would close the remaining gap, but nothing critical 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% and the `direction` enum is fully documented in the schema, so the baseline is 3. The description's mention of "incoming entries" loosely ties to the `incoming` value but adds no format or default detail beyond the schema.

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 opens with a specific verb and resource - listing shares both sent and received by this user - which is unambiguous. It clearly distinguishes this read operation from the mutation siblings create_share/delete_share by describing scope, though it never names those siblings as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete downstream guidance: incoming entries are read by passing `sharing_fulcra_userid` as `fulcra_userid` to the file and data tools, and a `group_id` points the agent at `get_groups`. That routes the agent correctly after the call, but it offers no explicit statement of when to pick this over other listing tools or any exclusions.

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