Skip to main content
Glama
blakeyoder

TypeScript Definitions MCP Server

by blakeyoder

get_project_info

Retrieve details about the current TypeScript project to access type definitions and interface structures from dependencies for generating type-safe mocks and test data.

Instructions

Get information about the current TypeScript project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the get_project_info tool. It retrieves installed packages using WorkspaceDetector and returns project configuration along with package statistics.
    private async handleGetProjectInfo() {
      const packages = WorkspaceDetector.getInstalledPackages(this.config.rootPath);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              config: this.config,
              installedPackages: packages.length,
              packagesWithTypes: packages.filter(p => p.hasTypes).length,
              packages: packages.slice(0, 20) // Limit to first 20 for readability
            }, null, 2)
          }
        ]
      };
    }
  • The input schema definition for the get_project_info tool, specifying an empty object with no properties.
    inputSchema: {
      type: "object",
      properties: {},
      additionalProperties: false
    }
  • The tool registration entry in the ListToolsRequestSchema response, defining the name, description, and input schema for get_project_info.
    {
      name: "get_project_info",
      description: "Get information about the current TypeScript project",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false
      }
    },
  • The dispatch case in the CallToolRequestSchema switch statement that routes calls to get_project_info to its handler.
    case "get_project_info":
      return await this.handleGetProjectInfo();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets information,' implying a read-only operation, but doesn't specify what kind of information (e.g., configuration, dependencies, structure) or any constraints like performance, permissions, or output format, leaving significant gaps.

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 a single, clear sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and appropriately sized for a simple tool, making it highly efficient and easy to understand.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate but lacks depth. It doesn't explain what 'information' includes or how it relates to sibling tools, which could leave the agent uncertain about when and how to use it effectively in context.

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 has 0 parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description appropriately doesn't discuss parameters, which is efficient, but it doesn't add any semantic context beyond the schema, so it doesn't reach the highest score.

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?

The description clearly states the action ('Get information') and the target resource ('current TypeScript project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'get_package_types' or 'lookup_type', which might also provide project-related information, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_package_types' and 'lookup_type' that might overlap in functionality, there's no indication of when this tool is preferred or what specific context it serves, leaving usage ambiguous.

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/blakeyoder/typescript-definitions-mcp'

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