Skip to main content
Glama

List Platform Agent Tools

talonic_list_agent_tools
Read-onlyIdempotent

Lists the platform’s agent tools, their input schemas, and whether your credential can invoke each, so you can find a capability not covered by direct tools and call it via the invocation tool.

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 credential 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 }.

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_agent_tools"
  }
}

Input 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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered; the description adds genuinely new behavioral context: results are filtered by what THIS credential may invoke, the flag defaults govern that filtering, and the response shape (tools[], invocable_count, totalCount) is spelled out. It doesn't mention pagination or any cap on registry size, which is the one behavioral gap for a potentially large listing.

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 purpose sentence followed by clearly labeled USE WHEN / NOT FOR / ARGS / RETURNS blocks — very scannable. The parenthetical tool-name list and nested em-dash clauses run slightly long, but each block still carries distinct routing value.

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?

No output schema exists, but the description compensates with an explicit return shape including field names and the invocable/total counts. Combined with the documented args, defaults, and the downstream invoke tool, an agent has everything needed to call this and act on the result.

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 coverage is 100% so the baseline is 3, and the description goes further by giving both booleans with their defaults and the intent behind them ('hide tools this credential cannot run', 'include each tool's JSON input schema'). Nothing about consequences or interaction between the two flags (e.g. that schemas for non-invocable tools are hidden) is stated, keeping it below a 5.

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?

Specific verb and resource ('List the platform's agent tool registry'), with an enumeration of what's in the registry (find_data, describe_data, query_data, get_document_markdown, workspace_overview) and the per-credential invocability flag. The NOT FOR line explicitly separates it from the sibling listing tools (talonic_list_fields, talonic_find_data, talonic_search), so an agent can route without opening a 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?

USE WHEN names the exact trigger (a capability the talonic_* tools don't cover) and even closes the loop by pointing at talonic_invoke_agent_tool as the follow-up call. NOT FOR names three concrete alternatives with the reason ('those are shaped for you'), leaving nothing to inference.

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