Skip to main content
Glama
Sign In
cursor-sdk-mcp

cursor-sdk-mcp

by newxun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cursor: list models

cursor_list_models
Read-only

Retrieve the list of available Cursor models for your account. Use the returned model IDs to specify a model for agent runs.

Instructions

List the Cursor models available to the configured account. Use the returned ids as the model argument for cursor_run_agent / cursor_follow_up.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cursor_list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already provide readOnlyHint and openWorldHint, so the description's main addition is the usage of returned ids. It confirms the read-only nature but does not disclose further behavioral traits like pagination or result format. Adequate given 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?

Two sentences, front-loaded with the core purpose, and every word adds value. No wasted text.

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?

For a zero-parameter list tool with strong annotations, the description is complete. It explains the output's purpose (model ids for sibling tools) and the scope (available to account). 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?

The input schema has zero parameters with 100% coverage, so the description does not need to add parameter details. The description provides no param info, which is appropriate.

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 lists Cursor models available to the configured account, with a specific verb ('List') and resource ('Cursor models'). It distinguishes from siblings by explaining how the returned ids are used with cursor_run_agent and cursor_follow_up.

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 explicitly tells the agent to use returned model ids as the `model` argument for two sibling tools, providing clear context. It does not include when-not-to-use or alternative tools, but the guidance is strong.

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