Skip to main content
Glama

concentration_check

Calculate the concentration saving-throw DC after damage, and optionally resolve whether concentration holds by including the d20 result and Constitution modifier.

Instructions

Compute the Concentration saving-throw DC when a concentrating creature takes damage: DC = max(10, damage // 2), capped at 30 (SRD 5.2.1 p.179). Optionally pass d20_result (+ con_modifier) to also resolve whether concentration holds. Returns data {dc[, total, success]}. The caller rolls; srdcheck folds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
damageYesdamage taken while concentrating
d20_resultNooptional: the rolled d20 for the Constitution save
request_idNo
con_modifierNoConstitution save modifier (used only if d20_result is given)
table_policyNo
asserted_factsNo
policy_contextNo
table_decisionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
whyYes
dataNo
factsYes
adapterYes
verdictYes
rule_idsYes
citationsYes
exit_codeYes
assumptionsYes
explanationYes
rule_resultYes
checked_scopeYes
coverage_levelYes
state_mutationYes
table_decisionYes
unchecked_scopeYes
Behavior5/5

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

With no annotations, the description fully explains behavior: deterministic DC formula, optional d20 check, return shape, and the caller-rolls convention. No side effects or hidden behaviors are involved for this pure computation tool.

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 two sentences, front-loads the formula, then states optional behavior and return values. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Despite the large schema, the description covers the essential domain logic and return shape. The output schema exists, and the tool is a focused calculation, so the description is complete enough for an agent to select and invoke it correctly.

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?

Schema coverage is low (38%), so the description compensates by explaining the key parameters: damage, d20_result, and con_modifier, including their optional relationship. It does not explain infrastructure params like table_policy or asserted_facts, but those are secondary to the tool's core purpose.

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?

The description uses a specific verb ('Compute'), identifies the resource ('Concentration saving-throw DC'), and includes the exact formula and cap. It also distinguishes itself from sibling check-related tools by noting the caller rolls and 'srdcheck folds.'

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

Usage Guidelines4/5

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

The description clearly states when to use the tool ('when a concentrating creature takes damage') and explains the optional d20 resolution path. It lacks explicit named alternatives, but the context and division of responsibility are clear enough.

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/chaoz23/srdcheck'

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