Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Cache Runs

cache_runs
Idempotent

Cache runs to disk by fetching with optional filters for repeatable access.

Instructions

Fetch and cache runs to disk with optional filters for efficient repeated access.

Args:

  • runType (enum, optional): Filter by 'deploy' or 'refresh'

  • runStatus (enum, optional): Filter by 'completed' | 'failed' | 'canceled' | 'running' | 'waitingToRun'

  • environmentID (string, optional): Filter by environment ID

  • detail (boolean, optional): Fetch expanded run details. Defaults to false

  • 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 run details. Defaults to false.
orderByNoOptional sort field used for paginated collection. Defaults to id.
runTypeNoOptional run type filter
pageSizeNoOptional API page size used while collecting the full snapshot. Defaults to 250.
runStatusNoOptional run status filter
environmentIDNoOptional environment ID filter
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
Behavior4/5

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

The description adds context beyond annotations: it reveals side effect (caching to disk), idempotency (efficient repeated access), and return format (resourceUri). Annotations provide idempotentHint=true, which aligns. No contradictions.

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?

Description is well-structured with Args and Returns sections, front-loading the main purpose. It is adequately concise, though could be tightened by removing redundant default mentions.

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 7 optional params and no output schema provided, the description explains the return format (cache metadata with resourceUri) adequately. It covers the essential behavior for an agent to use the tool correctly.

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 description adds marginal value. It provides defaults and limits (e.g., pageSize max 500) and clarifies parameter purposes, but does not introduce new 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 'Fetch and cache runs to disk with optional filters', using specific verb (fetch/cache) and resource (runs). It distinguishes from siblings like 'list_runs' and 'get_run' by emphasizing caching behavior.

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 explicit guidance on when to use this tool vs alternatives (e.g., 'list_runs' for one-time fetch). The description implies caching for repeated access, but does not state exclusions or alternatives.

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