Skip to main content
Glama
geoffwhittington

SD Elements MCP Server

get_project

Retrieve detailed information about a specific project by providing its ID, with options to include and expand additional fields for comprehensive insights.

Instructions

Get detailed information about a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expandNoFields to expand (comma-separated)
includeNoAdditional fields to include (comma-separated)
project_idYesThe ID of the project to retrieve

Implementation Reference

  • The core handler function for the 'get_project' MCP tool. It is decorated with @mcp.tool(), which registers it with the MCP server. The function fetches project details via api_client.get_project and returns JSON.
    @mcp.tool()
    async def get_project(ctx: Context, project_id: int, page_size: Optional[int] = None, include: Optional[str] = None, expand: Optional[str] = None) -> str:
        """Get details of a specific project. Use list_countermeasures to see countermeasures for a project, not this tool."""
        global api_client
        if api_client is None:
            api_client = init_api_client()
        params = build_params({"page_size": page_size, "include": include, "expand": expand})
        result = api_client.get_project(project_id, params)
        return json.dumps(result, indent=2)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get detailed information' implies a read operation, it doesn't specify authentication requirements, rate limits, error conditions, or what constitutes 'detailed information' in the response format. The description is too vague about the actual behavior beyond the basic retrieval concept.

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 perfectly concise - a single sentence that communicates the core purpose without any wasted words. It's front-loaded with the essential information and doesn't include unnecessary elaboration or redundant phrasing.

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?

For a read operation with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, whether authentication is required, what happens with invalid project IDs, or how the optional parameters affect the response. Given the lack of structured metadata, the description should provide more operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents all three parameters. The description doesn't add any additional meaning about parameters beyond what's in the schema - it doesn't explain how 'expand' and 'include' differ, provide examples of valid values, or clarify the relationship between these optional parameters.

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 verb ('Get') and resource ('detailed information about a specific project'), making the purpose immediately understandable. It distinguishes from list_projects by specifying retrieval of a single project, but doesn't explicitly contrast with other get_* tools that retrieve different resource types.

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. It doesn't mention when to use get_project versus list_projects, nor does it provide any context about prerequisites, permissions needed, or typical use cases for retrieving project details.

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

Related 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/geoffwhittington/sde-mcp'

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