Skip to main content
Glama
Sign In

Shareflo

by uk.co.shareflo
OverviewDiscussionsAdmin

get_holdings

Read-only

Lists the confirmed holdings of shares, options and other instruments in the company, one line per holding, each with the holding_uid that the share-action tools (stop_vesting, exercise_options, cancel_shares_or_options, transfer_shares, convert_share_class, amend_vesting) require. Filter by stakeholder, instrument or both; with neither, it returns every holding. A unique part of a name (such as a surname) is enough; when several records match, the reply lists them so you can ask the user which one. A stakeholder can hold several separate grants of the same instrument: when more than one holding matches what the user describes, ask which one, using the acquisition date and quantity, rather than guessing. Requires unlock_shareflo to have been called first.

Input Schema

NameRequiredDescriptionDefault
stakeholderNoStakeholder name, or a unique part of it such as a surname. Omit to include every stakeholder.
instrument_nameNoInstrument name, or a unique part of it, e.g. Ordinary or Series A. Omit to include every instrument.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / instrument_name
      Added value: +{
+  "description": "Instrument name, or a unique part of it, e.g. Ordinary or Series A. Omit to include every instrument.",
+  "type": "string"
+}
    • changedInput schema / properties / stakeholder / description
      Previous value: -"Stakeholder name to filter by."New value: +"Stakeholder name, or a unique part of it such as a surname. Omit to include every stakeholder."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and does so well: it discloses the unlock_shareflo prerequisite, the one-line-per-holding return shape with holding_uid, and the disambiguation protocol when several records match. These are behavioral traits well beyond what the annotation provides.

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?

Front-loaded with the core purpose and the holding_uid rationale, and every sentence is relevant. However, the multi-match disambiguation guidance is spread over two sentences that partially restate each other ('when several records match, the reply lists them' vs. 'when more than one holding matches... ask which one'), which is mild redundancy.

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?

With no output schema, the description compensates by describing the return shape, and it covers the prerequisite, the filter matrix, and the ambiguity-handling flow. An agent has everything needed to select and call this tool correctly without opening any sibling.

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?

Schema description coverage is 100%, so both parameters are already documented and the baseline is 3. The description still adds combination semantics the schema does not state, namely that the two filters are combinable and that omitting both returns all holdings, which is genuine meaning beyond the field-level text.

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?

States a specific verb and resource ('Lists the confirmed holdings of shares, options and other instruments in the company') with the scope of what each line contains. It is clearly distinguishable from sibling readers such as get_instruments and get_stakeholders, and it explicitly ties itself to the share-action tools as the source of holding_uid.

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?

Spells out when to use each filter mode: filter by stakeholder, by instrument, or both, and with neither it returns everything. It names the six downstream tools that consume the returned holding_uid, establishing why and when an agent should call it, and states the unlock_shareflo prerequisite.

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

All Shareflo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources