MadeCheck

Accept compliance quote

accept_compliance_quote

Accept compliance quote. Accept the compliance_case_id for free using request_id; returns completion state, zero charged_cents and any free-file queue notice. File preparation is free; new requests share a limit of three per email in 30 days and 20 starts per UTC day, with extras queued. 接受报价。用 compliance_case_id、request_id 免费受理补齐包；返回受理状态、charged_cents=0 和排队提示。文件免费；新单同邮箱30天最多开始3单，全站UTC日最多开始20单，超额排队。

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": {
      "request_id": "<request_id>",
      "compliance_case_id": "<compliance_case_id>"
    },
    "name": "accept_compliance_quote"
  }
}

Input Schema

Name	Required	Description	Default
`request_id`	Yes
`source_tag`	No
`compliance_case_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

addedInput schema / properties / source_tag

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedOct 24, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the operation is free, charged_cents is zero, completion state and a queue notice are returned, and requests are limited to three per email in 30 days and 20 starts per UTC day with extras queued. It does not fully clarify retry or idempotency behavior, but the rate-limit and cost details add substantial value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The English portion is front-loaded and efficient, moving from action to return values to limits. The full Chinese translation duplicates the same information, which is understandable for a bilingual audience but adds avoidable length for an agent-facing definition.

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?

The description covers the mutation's purpose, cost, return state, and rate-limit queue behavior, which is meaningful because there is no output schema. Completeness is weakened by the missing source_tag semantics and limited edge-case guidance for repeated or invalid acceptance requests.

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%, so the description must carry parameter meaning. It explains that request_id is used to accept and that compliance_case_id identifies the case, but source_tag is entirely undocumented in both schema and description, leaving one of three parameters without semantic guidance.

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: accept a compliance quote using request_id and compliance_case_id. It makes the operation's free nature and queued completion state clear, though it does not explicitly distinguish itself from sibling compliance-check or material tools.

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 implied by 'Accept compliance quote' and the explanation that file preparation is free and subject to queue limits. However, there is no explicit when-to-use guidance versus alternatives such as request_compliance_check, nor any when-not-to-use conditions.

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

All MadeCheck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?