Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Cache Workspace Nodes

cache_workspace_nodes
Idempotent

Caches a complete snapshot of all workspace nodes to disk for offline access and bulk analysis.

Instructions

Fetch and cache the ENTIRE workspace's nodes to disk — a full snapshot of every node. Run this ONLY when the user explicitly wants the whole workspace cached. For targeted work, prefer search_workspace_content, get_workspace_node, or get_workspace_subgraph; for a profile use analyze_workspace_patterns. detail=false is much cheaper and sufficient for inventory; detail=true on a large workspace produces a very large snapshot. Note: the result is a coalesce://cache/... resource link, which clients that do not support MCP resources (e.g. Snowflake Cortex Code) cannot read.

Args:

  • workspaceID (string, required): The workspace ID

  • detail (boolean, optional): Fetch expanded node details. Defaults to true

  • pageSize (number, optional): API page size for collection. Defaults to 250, max 500

  • orderBy (string, optional): Sort field for paginated collection. Defaults to id

  • orderByDirection ('asc'|'desc', optional): Sort direction

Returns: Cache metadata with resourceUri (coalesce://cache/...) for accessing the cached data via MCP resource read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNoWhen true, fetches expanded node details. Defaults to true.
orderByNoOptional sort field used for paginated collection. Defaults to id.
pageSizeNoOptional API page size used while collecting the full snapshot. Defaults to 250.
workspaceIDYesThe workspace ID
orderByDirectionNoOptional sort direction used for paginated collection.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNo
fileUriNo
messageNo
metaUriNo
orderByNo
runTypeNo
cachedAtNo
pageSizeNo
toolNameNo
pageCountNo
runStatusNo
sizeBytesNo
totalRunsNo
autoCachedNo
totalNodesNo
totalUsersNo
resourceUriNo
workspaceIDNo
environmentIDNo
maxInlineBytesNo
orderByDirectionNo
Behavior5/5

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

Adds context beyond annotations: details trade-off (detail=false cheaper vs detail=true large snapshot), and client limitation (result resource link unreadable by clients like Snowflake Cortex Code). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with main purpose, Args section, Returns section. Front-loaded with key info, no wasted words.

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 caching tool with 5 params and output schema. Explains caching mechanism, resource link limitation, parameter behaviors. No gaps.

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 100% gives baseline 3. Description adds value: explains detail parameter cost trade-off, pageSize for collection, orderBy/orderByDirection for pagination. Above 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?

The description clearly states the tool fetches and caches the entire workspace's nodes to disk, specifying the resource (workspace nodes) and action (fetch and cache). It distinguishes from siblings like search_workspace_content, get_workspace_node, etc.

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?

Explicitly says 'Run this ONLY when the user explicitly wants the whole workspace cached' and provides specific alternatives for targeted work (search_workspace_content, get_workspace_node, get_workspace_subgraph, analyze_workspace_patterns).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Coalesce-Software-Inc/coalesce-transform-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server