Skip to main content
Glama
sweetwisdom

MCP Project Query Server

by sweetwisdom

get_project_all

Retrieve all projects managed by the MCP Project Query Server to view and organize project data for management and query purposes.

Instructions

获取全部项目

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_project_all' MCP tool. Defines input schema (empty), description, and inline handler that delegates to ProjectController.getAllProjects().
    server.tool(
        'get_project_all',
        '获取全部项目',
        {},
        async () => {
            return projectController.getAllProjects();
    
        }
    );
  • Handler logic in ProjectController: fetches all projects from service and formats as MCP response with JSON stringified content.
    getAllProjects(): { content: Array<{ type: "text"; text: string }> } {
      const projects = this.projectService.getAllProjects();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projects),
          },
        ],
      };
    }
  • Helper method in ProjectService that delegates getAllProjects to the repository.
    getAllProjects(): Project[] {
      return this.projectRepository.getAllProjects();
  • Core implementation in ProjectRepository: returns the in-memory array of loaded projects from JSON file.
    getAllProjects(): any[] {
      return this.projects;
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. It only states the action ('获取全部项目') without disclosing behavioral traits like pagination, sorting, filtering, rate limits, authentication needs, or what 'all' entails (e.g., archived projects). This is inadequate for a tool with zero annotation coverage.

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 a single, efficient phrase ('获取全部项目') that's front-loaded and wastes no words. However, it's under-specified rather than concise, as it lacks necessary details for clarity, but it's not verbose or poorly structured.

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

Completeness2/5

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

Given the complexity (a read operation with no parameters but potential behavioral nuances), no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error handling, or operational constraints, leaving significant gaps for an AI agent to understand how to use it effectively.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it correctly implies no filtering or options are available. Baseline is 4 for zero parameters, as it aligns with the schema.

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

Purpose3/5

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

The description '获取全部项目' (Get all projects) states a clear verb ('获取' - get) and resource ('项目' - projects), but it's vague about scope and doesn't differentiate from siblings like 'get_project_count' or 'get_project_info'. It's better than a tautology but lacks specificity about what '全部' (all) means in practice.

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?

There's no guidance on when to use this tool versus alternatives like 'get_project_info' (for specific project details) or 'get_project_count' (for just the number). The description implies a comprehensive retrieval, but it doesn't specify prerequisites, exclusions, or contextual usage scenarios.

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/sweetwisdom/mcp-demo'

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