Skip to main content
Glama
onigetoc

MCP Context Master

by onigetoc

add_project_context

Adds project context for a library using exact package names, with optional topic focus and token amount.

Instructions

Adds knowledge context for a library using EXACT package names from package.json or confirmed library names. If you're unsure about the exact library name, use the search workflow first: 1) Search GitHub for the library, 2) Confirm the correct repository, 3) Use this tool with the exact name. For example: Use 'remotion' (not '@remotion/captions'), 'react' (not 'react-dom'), '@tanstack/react-query' (not 'react-query'). If the user mentions a feature or topic (like 'captions', 'routing'), that should be used as a topic parameter, not as part of the library name. IMPORTANT: Always provide the absolute path to the user's project directory as projectPath parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional topic to focus the documentation (e.g., 'srt caption', 'authentication', 'routing'). This helps Context7 provide targeted documentation and saves tokens.
tokensNoNumber of tokens to request from Context7 (between 2000 and 10000). Default: 3000. Use higher values for broader overviews, lower values for specific features.
libraryNameYesThe name of the library to add (e.g., 'react', '@reduxjs/toolkit', 'remotion').
projectPathNoREQUIRED: Absolute path to the user's project directory (e.g., C:\Users\Name\projects\my-app or /home/user/projects/my-app). The MCP server cannot automatically detect the user's project location - you must provide it explicitly.
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the exact-name requirement, the projectPath requirement (cannot be auto-detected), and the topic distinction. However, it doesn't describe the operation's outcome or whether it overwrites existing context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed but well-structured with a numbered workflow and illustrative examples. Each sentence contributes meaning, though it could be tightened slightly without losing value.

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 tool with four parameters and no output schema or annotations, the description is thorough: prerequisites, parameter nuances, and usage examples are all covered. It lacks only a statement about return values or confirmation behavior, which is a minor gap.

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 schema already covers all parameters at 100%, but the description adds critical semantics: exact naming rules, topic vs library distinction, and the mandatory nature of projectPath (despite not being in the required array). This goes beyond the schema's basic examples.

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 adds knowledge context for a library and emphasizes EXACT package names, distinguishing it from search_library_advisor and other sibling tools. The verb 'adds' plus the resource 'knowledge context for a library' makes the purpose unambiguous.

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

Usage Guidelines5/5

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

Explicitly instructs to use the search workflow when unsure of the library name, provides step-by-step guidance, and clarifies when to use topic vs libraryName. Also notes that projectPath must always be provided, giving clear when/how to use guidance.

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/onigetoc/mcp-context-master'

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