Skip to main content
Glama

Ask Cursor (new chat)

cursor_ask

Submit a question or task to Cursor CLI in a new chat. Returns the agent's final message using your Cursor login and optional workspace context.

Instructions

Ask the Cursor CLI (cursor-agent -p) a question or task in a NEW chat.

Uses your existing Cursor login (OS credential store, or a CURSOR_API_KEY env var — see cursor_status). Returns the agent's final message, read straight from stdout (no scraping). Cursor is a capable agentic coder with a wide model menu (GPT / Claude / Grok / Composer); point workspace at a project dir for context-aware answers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOptional model override (`--model`, e.g. "gpt-5.2", "sonnet-4-thinking", "auto"); validated against `cursor-agent models` and rejected on a typo. Omit to use your Cursor default.
watchNoIf true, open a live "watch" view streaming cursor's steps from its `--output-format stream-json` event stream. Same final text is returned. Best-effort. Default false.
promptYesQuestion or instruction for Cursor.
sandboxNoPermission policy (maps to cursor's mode/force flags): "read-only" (default — `--mode ask`: agent-enforced, no file/shell edits; NOT an OS sandbox, so unlike codex it is not a hard boundary), "workspace-write" (may edit files, rooted at the workspace), or "danger-full-access" (OS sandbox off — avoid).read-only
timeout_sNoMax seconds to wait for cursor to complete. Default 180.
workspaceNoWorking root for the chat (`--workspace`). Defaults to the server cwd.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: authentication method, return format (stdout, no scraping), sandbox policies with caveats ('NOT an OS sandbox'), and the fact that workspace provides context-aware answers. Combined with annotations, the agent has a clear picture of side effects and behavior.

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 very concise (3-4 sentences), front-loaded with the main action, and each sentence adds essential context. No wasted words.

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?

The description covers purpose, authentication, return value, sandbox, and workspace advice. Given the rich schema and output schema, it is mostly complete. It could mention timeout_s default or error scenarios, but those are in schema.

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 baseline is 3. The description adds minimal new meaning beyond the schema—only a brief usage hint for workspace and sandbox. It does not repeat or significantly enhance parameter explanations.

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 states exactly what the tool does: 'Ask the Cursor CLI a question or task in a NEW chat.' It distinguishes from siblings by specifying 'NEW chat' and mentions the underlying CLI command and capability.

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

Usage Guidelines4/5

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

The description implies usage context (new chat vs. continue) and references cursor_status for authentication. It could be more explicit about when to use this tool over alternatives like cursor_continue or other AI ask tools.

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/SinanTufekci/agent-intern'

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