Skip to main content
Glama
Sign In
insight-blueprint

insight-blueprint

by etoyama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

suggest_cautions

Identify potential cautions for specified tables by matching their columns against domain knowledge entries, helping you uncover risks before analysis.

Instructions

Suggest cautions for the given table/source names.

Searches all domain knowledge entries (catalog and extracted) by matching affects_columns against provided table names.

Args: table_names: Comma-separated string of table/source names

Returns: dict with table_names, cautions, count

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": {
      "table_names": "<table_names>"
    },
    "name": "suggest_cautions"
  }
}

Input Schema

NameRequiredDescriptionDefault
table_namesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that it searches 'all domain knowledge entries (catalog and extracted)' via affects_columns matching, and specifies the return dict with table_names, cautions, and count. This provides useful transparency for a read-only suggestion tool, though edge cases are not discussed.

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?

The description is well-structured with a purpose sentence, a behavior sentence, and clear Args/Returns sections. There is no wasted text; every sentence adds 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?

For a simple one-parameter tool with an output schema, the description is complete: it explains the search behavior, the argument format, and the return structure. No critical aspects are missing for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema describes table_names only as a string with no description. The description adds that it is a 'comma-separated string of table/source names', fully clarifying the expected format and meaning beyond the schema. This compensates for the 0% schema coverage.

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?

The description clearly states the tool 'suggests cautions for the given table/source names', a specific verb+resource. It further differentiates from siblings by describing the matching against affects_columns in domain knowledge entries, distinguishing it from generic search or knowledge retrieval tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied: when you have table/source names and need cautions, this tool searches domain knowledge. However, there is no explicit mention of when not to use it or alternatives like search_catalog or get_domain_knowledge, so guidance is not fully developed.

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