modelcontextprotocol / modelcontextprotocol/servers

`sequentialthinking`'s tool definition costs ~921 tokens/session; about half duplicates the schema's own parameter descriptions

Open Beginner friendly
#4,507 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
90.5k
Forks
11.7k
Avg merge
2d 2h
Merged PRs (30d)
5

Description

The server advertises one tool whose definition costs ~921 tokens (tiktoken cl100k; ~566 of that is the description). Every session that connects the server pays this whether the tool is used or not.

Two description sections look droppable at no semantic cost: "Parameters explained" restates the description that all 9 inputSchema parameters already carry (clients send both, so the text is paid twice), and "Key features" describes the tool's virtues rather than when to call it. Keeping the intro + "When to use this tool" yields the same selection signal at ~463 tokens (50% less) — measured on the published package, method + script: https://github.com/lCrazyblindl/lap/blob/main/docs/UPSTREAM-ISSUES.md.

Happy to send the trim as a PR if the direction sounds right. (Disclosure: I maintain lap, the measurement tool used; MIT, no product.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the published sequentialthinking package's tool definition and read docs/UPSTREAM-ISSUES.md for the measurement method and script. Remove the duplicated “Parameters explained” and “Key features” sections while retaining the intro and “When to use this tool,” then rerun the measurement to confirm the definition is about 50% smaller.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.