Skip to main content
Glama

Proportion Survey Sample Size

bpj_survey_sample_size
Read-onlyIdempotent

Estimate the size of a simple random sample for an expected proportion and a 95% margin of error.

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": {
      "expectedPercent": "<expectedPercent>",
      "marginPoints": "<marginPoints>",
      "population": "<population>"
    },
    "name": "bpj_survey_sample_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
populationYes
marginPointsYes
expectedPercentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and mutability are covered. The description adds one genuinely useful constraint: the confidence level is fixed at 95%, which is not a parameter and cannot be changed. However, it says nothing about the return value, does not mention that it uses finite-population correction, and gives no caveats.

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?

It is a single sentence of about twenty words with no filler. The resource comes first (sample size for a proportion), and the constraints follow.

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?

For a three-parameter, read-only, closed-world calculator with no output schema, the definition covers the core intent but leaves an agent guessing about the population=0 convention for an unknown population, about how the returned value should be interpreted, and about why population is a required value rather than optional.

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% and the conventions that matter most are in the parameter titles, not in the description: population=0 means unknown, expectedPercent=50 means use 50 when you do not know the value, and marginPoints is given in percentage points. The description names the proportion and margin but does not explain the population parameter or any of these conventions, so it does not compensate for the empty schema descriptions.

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 names a specific verb and resource: estimating a simple random sample size for a proportion, and it states the key modeling assumption (simple random sample, 95% confidence). It does not point to any sibling tool as an alternative, but among the listed siblings none is a near-duplicate, so the purpose is still unambiguous.

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?

Usage is only implied by the stated assumptions: use it for a proportion with a fixed 95% confidence level. There is no explicit statement of when to avoid it, such as non-random designs, comparisons of two proportions, or other confidence levels, and no alternative is named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.