Skip to main content
Glama

Create Account

talonic_create_account

Creates a separate account for a new company so its documents stay isolated and answers never mix in another company's files. Use before adding files for a company not yet listed.

Instructions

Create an account: a company whose documents the workspace keeps apart, so answers about it never mix in another company's files.

USE WHEN: the user is about to add files for a company that talonic_list_accounts does not show yet. NOT FOR: tagging single documents · a company that already exists (reuse its name). ARGS: name; optional aliases[] (other names it appears under, e.g. its legal name), description. RETURNS: { id, name, aliases[], description, created_at }. 409 when the name is taken.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "talonic_create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name, e.g. 'Filu'.
aliasesNoOther names, e.g. ['Filu Group GmbH'].
descriptionNoOptional description.

Output Schema

NameRequiredDescriptionDefault
idYesAccount id.
nameYesCompany name.
aliasesYesOther names the company appears under.
created_atNoISO 8601 creation time.
descriptionNoFree-text description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.94

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint false, destructiveHint false, idempotentHint false, openWorldHint false), so the bar is lower. The description still adds real value by disclosing the 409 conflict when the name is taken and the isolation consequence of creating an account, though it says nothing about who may create accounts or whether creation is reversible.

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?

Labeled sections (USE WHEN / NOT FOR / ARGS / RETURNS) front-load the routing decision and keep every sentence functional. The only redundancy is restating the return fields covered by the output schema and the argument names covered by the schema.

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 3-parameter creation tool with full annotation coverage and an existing output schema, the definition covers purpose, routing, arguments, return shape, and the main failure mode. It is complete enough to call correctly; only permission/ownership behavior is left unstated.

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 all three parameters are already documented with examples and constraints. The description adds modest meaning for aliases ('other names it appears under, e.g. its legal name'), clarifying intent rather than format, which is a small step above the schema baseline.

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 plus the defining semantic: an account is 'a company whose documents the workspace keeps apart, so answers about it never mix in another company's files.' That isolation framing lets an agent distinguish it from sibling tools like talonic_ask or talonic_extract without opening any 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?

Gives an explicit USE WHEN trigger (adding files for a company talonic_list_accounts does not yet show) and explicit NOT FOR cases (tagging single documents; a company that already exists — reuse its name). This is exactly the when/when-not/alternative structure that removes ambiguity.

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