Escalate Anything

Overview Schema Source Related Servers Discussions Admin

Record a bill

bill_record

Record a bill's company, amount due, period end, and optional promo end to track due dates and support complaint escalation cases.

Instructions

Record one bill (total amount due for the period ending period_end, YYYY-MM-DD). promo_end is the date a promotional price ends, if the bill shows it.

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": {
      "company": "<company>",
      "period_end": "<period_end>",
      "amount": "<amount>"
    },
    "name": "bill_record"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No
`plan`	No
`amount`	Yes
`company`	Yes
`promo_end`	No
`period_end`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. Beyond that, the description says nothing about what happens on a repeat record (idempotency or duplication), whether values are overwritten, or what confirmation is returned, which matters for a write tool.

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 zero filler, and the core purpose is front-loaded ahead of the date-parameter clarifications. The brevity is efficient rather than padded, though the second sentence only serves one optional parameter.

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?

An output schema exists, so return values need not be described. But for a six-parameter write tool with 0% schema coverage and no usage routing against bill_check, the definition leaves too much for the agent to infer before calling.

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 six parameters, so the description must carry the load — it explains only period_end (period-ending date, YYYY-MM-DD) and promo_end. The three required-core parameters company, amount (only obliquely via 'total amount due'), and plan, note are left without added meaning.

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 states a specific verb and resource — 'Record one bill' — and narrows scope with 'total amount due for the period ending period_end'. It is clearly distinct from the query-style sibling bill_check, though it never names an alternative explicitly.

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?

There is no guidance on when to record versus check a bill (bill_check is the obvious counterpart), no mention of prerequisites such as the company needing to exist, and no mention of duplicate handling. The usage context is only implied by the verb 'record'.

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