Skip to main content
Glama
talonicdev

talonic-mcp

Official
by talonicdev
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

List Platform Agent Tools

talonic_list_agent_tools
Read-onlyIdempotent

Discover which agent tools (SQL queries, workspace overviews, provenance checks) this credential can invoke, with input schemas, before calling them via the invocation endpoint.

Instructions

List the platform's agent tool registry — every retrieval, provenance and analysis primitive the in-product Talonic agent runs on (find_data, describe_data, query_data for read-only SQL over the extracted data, get_document_markdown, workspace_overview, …) with its input schema and whether THIS credential may invoke it. Target API: https://talonic.com/docs/api (GET /v1/agent/tools).

USE WHEN: you want a capability talonic_* tools do not cover directly (e.g. SQL over the structured data, a workspace overview, cohort discovery) — list here, then call talonic_invoke_agent_tool with the tool name and its args. NOT FOR: discovering fields (talonic_list_fields / talonic_find_data) or documents (talonic_search) — those are shaped for you.

ARGS: only_invocable (default true — hide tools this key cannot run), include_schemas (default true — include each tool's JSON input schema). RETURNS: { tools[] of { name, description, impact, capability, can_invoke, input_schema? }, invocable_count, totalCount }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
only_invocableNoHide tools this credential cannot invoke. Default true.
include_schemasNoInclude each tool's JSON input schema. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.76

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds value beyond that: the credential-based can_invoke semantics, the read-only nature of the SQL primitives, and the explicit return shape. No contradiction with annotations.

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?

Well-structured with USE WHEN / NOT FOR / ARGS / RETURNS sections and front-loaded purpose. Slightly verbose with the enumerated primitive examples, but each section earns its place and improves scannability.

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?

Complete for a registry-listing tool: purpose, usage routing, argument defaults, return format, and credential semantics are all covered. With no output schema present, the RETURNS section is essential and it is provided in detail. Nothing an agent needs to call it correctly 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% so both parameters (only_invocable, include_schemas) are fully documented in the schema. The description restates them with defaults and meanings, which is redundant but confirms the semantics; baseline 3 is appropriate since the schema does the heavy lifting.

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 (List) and resource (the platform's agent tool registry) with concrete examples of what the registry contains. It distinguishes itself from siblings by explicitly naming talonic_list_fields/talonic_find_data and talonic_search as different discovery surfaces.

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?

Provides explicit USE WHEN (capability not covered by talonic_* tools directly, then invoke via talonic_invoke_agent_tool) and NOT FOR (fields/documents discovery) sections, naming exact alternatives. Nothing is left to inference.

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