Skip to main content
Glama

Create a population

create_population

Registers the population for a control as an explicit item list or declared size, up to 10,000 items, for internal-control sampling.

Instructions

Register the population for a control — either an explicit item list or a declared size. Bounded to 10000 items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engagementId": "<engagementId>",
      "description": "<description>"
    },
    "name": "create_population"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
periodNo
currencyNo
controlIdNo
descriptionYes
declaredSizeNo
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
populationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a write operation via 'Register' but is silent on permissions, idempotency, duplicate handling, whether items and declaredSize are mutually exclusive or must agree, and any mutation side effects. The 10000-item claim largely restates the schema's maxItems rather than adding new behavioral 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?

Two tight sentences with the purpose front-loaded and zero filler. The second sentence ('Bounded to 10000 items') is slightly redundant with the schema's maxItems constraint, which keeps it from being perfect, but it is short enough to earn its place.

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 7-parameter creation tool with 0% schema description coverage, the description omits how the five undocumented parameters interact and whether items and declaredSize are alternatives. An output schema exists, so return values need not be explained, but the input-side guidance is substantially incomplete.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate and mostly does not. It clarifies the items/declaredSize alternatives but leaves engagementId, description, controlId, period, and currency entirely unexplained, including whether controlId is optional scoping or required context.

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?

States a specific verb and resource ('Register the population for a control') and names the two operating modes (explicit item list vs declared size). An agent can distinguish this from list_populations and select_sample without opening any schema.

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

Usage Guidelines3/5

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

The phrase 'either an explicit item list or a declared size' gives mode selection guidance for the two central parameters, which is useful. However, it never says when to create a population at all versus using an existing one, nor does it state prerequisites such as the engagement or control needing to exist first.

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