Skip to main content
Glama
Sign In
ds-web-mcp

ds-web-mcp

by Ghubuserpym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

New DeepSeek session

new_session
Read-only

Creates an empty DeepSeek chat session and returns its ID and URL, so you can start a fresh conversation and continue it later through the ds-web-mcp server.

Instructions

Create an empty DeepSeek chat session and return its id and URL.

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": "new_session"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true; the description usefully discloses that the session starts empty and that the response carries an id and URL, which matters since there is no output schema. There is mild tension between 'Create' and readOnlyHint=true, but for an ephemeral, non-destructive session this reads as a harmless side effect rather than a contradiction; no auth, rate-limit, or lifecycle details are given.

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?

A single front-loaded sentence with no filler. The action and the return payload are both stated immediately.

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?

For a zero-parameter, no-output-schema tool, the description covers what it creates and what comes back (id and URL), which is the essential information. It stops short of saying what the URL is for or what the agent should do with the id next.

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 tool takes zero parameters, so there is nothing for the description to compensate for; baseline 4 applies. The description correctly signals that no configuration is required to open the session.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create an empty DeepSeek chat session') plus what is returned. It is clearly distinct from siblings like chat, upload_files, and list_files, though it never explicitly says how it relates to the chat tool it presumably feeds.

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?

Usage is only implied: an agent can infer you create a session before chatting, but the description never states when to call this versus 'chat' or whether an existing session can be reused. No prerequisites, no alternatives, no exclusions.

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