Skip to main content
Glama
Sign In
MCP Datadog Server

MCP Datadog Server

by ClaudioLazaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_cases_projects

Create new projects in Datadog to organize monitoring operations, log management, and metrics tracking for improved system oversight.

Instructions

Create a project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_cases_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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. 'Create a project' implies a mutation operation, but it doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on failure, or the response format. This is a significant gap for a mutation 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.

Conciseness5/5

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

The description is a single sentence with zero waste—'Create a project'—making it highly concise and front-loaded. Every word earns its place, though it may be overly minimal for clarity.

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 tool's mutation nature (implied by 'Create'), lack of annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't address key aspects like what a 'project' entails, success/failure behavior, or integration with sibling tools, leaving the agent with insufficient 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 input schema has 0 parameters with 100% description coverage, meaning no parameters are documented in the schema. The description doesn't mention parameters, which is appropriate since none exist. A baseline of 4 is applied as it doesn't need to compensate for missing param info.

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 'Create a project' clearly states the verb ('Create') and resource ('project'), making the basic purpose understandable. However, it doesn't specify what type of project (e.g., cases project, development project) or distinguish it from sibling tools like 'create_cases' or 'create_dashboards', leaving the scope vague.

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 many sibling tools starting with 'create_' (e.g., create_cases, create_dashboards), there's no indication of prerequisites, context, or differentiation, leaving the agent without usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools