agentleFS
Sign inStart free
MosoFinMosoFin/mosofin-mcp-plugin/skills/list-tools/SKILL.md

list-tools

Skill3 starsChanged 22 days agoMITView on GitHub

Show which MosoFin API operations are available for a connected datasource and their policy (maps to the get_datasource_tools MCP tool). Use when the user asks what data can be pulled, which financial data operations exist, or whether an operation is allowed.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. MosoFin/mosofin-plugins★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If MosoFin tools are absent, a call returns Unknown tool, or MosoFin reports that sign-in is required: the user is not signed in to MosoFin …

    line 15
  2. Very specific:

    If the platform has more than one connected company file (get_agent_datasources), ask which by display_name and pass its data_source_id — …

    line 25
  3. Very specific:

    Call get_datasource_tools with workspace_id, datasource (e.g.

    line 28
  4. Very specific:

    Write operations never appear: MosoFin is read-only by product boundary.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

List datasource tools

Wraps the server's get_datasource_tools tool: the catalog of allowed read operations plus effective policy. This is the only discovery path — inner operations like search_invoices are never top-level MCP tools, and a tool_name must never be invented. Full spec: docs/mcp-tool-spec.md §3.3.

If MosoFin tools are missing

If MosoFin tools are absent, a call returns Unknown tool, or MosoFin reports that sign-in is required: the user is not signed in to MosoFin in this host (this is not a company-file reconnect). Keep their request and follow /mosofin:connect (skills/connect/SKILL.md) to get them signed in from this conversation, then continue. Never say "refresh/reconnect". Do not invent catalog entries.

Steps

  1. Confirm workspace via list_workspaces if this chat has not already.
  2. If the platform has more than one connected company file (get_agent_datasources), ask which by display_name and pass its data_source_id — required, or the listing may not match.
  3. Call get_datasource_tools with workspace_id, datasource (e.g. quickbooks), and data_source_id when multi-entity.
  4. Present api_tools[] grouped by purpose (reports / search / get-by-id), with each tool's description and policy:
    • enabled — invocable now
    • permission — invocable; first call returns approval_required and needs a user yes before re-invoking with approved=true
    • disabled — blocked; do not invoke
  5. The listing is empty when there is no ACTIVE connection — route to /mosofin:connections for reconnect guidance.

Write operations never appear: MosoFin is read-only by product boundary. To actually run an operation, continue with /mosofin:run-tool or /mosofin:query-workspace.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free