Skip to main content
Glama

List Accounts

talonic_list_accounts
Read-only

List the workspace's accounts to see which companies or entities exist before uploading their files. Use it to find the account name needed when requesting an upload.

Instructions

List the workspace's accounts: the companies (portfolio companies, clients, entities) whose documents it keeps apart.

USE WHEN: before uploading a company's files (pass its name as account on talonic_request_upload), or to see which companies exist. NOT FOR: listing documents (talonic_search / talonic_filter) · creating an account (talonic_create_account). ARGS: none. RETURNS: data[] of { id, name, aliases[], description, created_at }.

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": "talonic_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesThe workspace's accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.94

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the conceptual meaning of an account (workspace-scoped, document partition) but says nothing about pagination, result limits, or ordering, which matters for a list endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-sentence purpose followed by labeled USE WHEN / NOT FOR / ARGS / RETURNS sections. Every sentence carries routing or behavioral information; nothing is padding.

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?

For a zero-arg read tool with full annotations and an output schema, this is essentially complete. The RETURNS block slightly duplicates the output schema, and pagination behavior is unaddressed, but nothing needed for correct invocation is missing.

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?

Zero parameters, so the baseline is 4; the description also states 'ARGS: none' explicitly, removing any doubt. It adds the useful note that an account name can be passed as `account` to talonic_request_upload, which is cross-tool semantics rather than this tool's own arguments.

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 ('List the workspace's accounts') and immediately defines the domain object as companies whose documents are kept apart, which disambiguates it from document-listing siblings. An agent can identify the right tool without opening the schema.

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?

Explicit USE WHEN clause names the downstream call (talonic_request_upload) and the precondition for chaining, and NOT FOR names talonic_search / talonic_filter for documents and talonic_create_account for creation. Both positive and negative routing are covered.

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