Skip to main content
Glama
Sign In
MCP Snowflake Server NSP

MCP Snowflake Server NSP

by nsphung
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

append_insight

Add a discovered insight from data analysis to the memo. Preserve key findings for later reference and context.

Instructions

Add a data insight to the memo

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": {
      "insight": "<insight>"
    },
    "name": "append_insight"
  }
}

Input Schema

NameRequiredDescriptionDefault
insightYesData insight discovered from analysis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits but only states the action. It does not disclose side effects (e.g., whether the memo is modified permanently), permissions needed, or return behavior beyond 'add'.

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 a single, clear sentence with no unnecessary words. It is front-loaded and concise for a simple tool.

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?

Given the tool's simplicity, the description is mostly adequate. It identifies the action and parameter, though it could be more explicit about which memo (e.g., current context) and whether it appends or replaces.

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?

The single parameter 'insight' has a description in the schema ('Data insight discovered from analysis'), and schema description coverage is 100%. The tool description adds no further meaning beyond the schema.

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 action ('Add') and the resource ('data insight to the memo'), with a specific verb and resource that distinguishes it from sibling tools (e.g., describe_table, read_query).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any context about prerequisites or exclusions. The description only states the function without usage context.

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