Skip to main content
Glama

run_paragraph

Executes a specified paragraph within a Zeppelin notebook and returns the output, enabling AI assistants to run and retrieve results from data engineering workflows.

Instructions

Execute a single paragraph and return its output. This is a synchronous call that waits for execution to complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notebookIdYesThe notebook ID
paragraphIdYesThe paragraph ID
Behavior3/5

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

States synchronous and waiting behavior, but lacks details on idempotency, error handling, or side effects. Annotations absent so description carries burden.

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?

Two concise, front-loaded sentences with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing output schema and annotations; description does not cover return format or error scenarios, but tool is simple.

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 100% with clear parameter descriptions; description adds nothing beyond 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?

Clear verb 'Execute' and resource 'paragraph' with distinction from 'run_all_paragraphs' and 'stop_paragraph'.

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?

Mentions synchronous behavior but no explicit when-to-use or when-not-to-use vs siblings.

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/mihneamanolache/zeppelin-mcp'

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