RateAPI — live US mortgage, auto, HELOC, personal & deposit rates

delete_cohort

Destructive

Permanently delete a saved cohort by id. This action cannot be undone.

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": {
      "id": "<id>"
    },
    "name": "delete_cohort"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Cohort id. Required.

Output Schema

Name	Required	Description	Default
`success`	No	True when the cohort was deleted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds meaningful context beyond the annotations by specifying 'Permanently delete' and 'This action cannot be undone,' which clarifies the irreversibility of the operation.

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?

A single, front-loaded sentence states the core action and key caveat. Every word earns its place, with no redundant or filler content.

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

Completeness4/5

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

For a simple one-parameter destructive operation with annotations already covering the danger profile and an output schema present, the description is largely complete. The irreversibility warning is valuable, and no critical missing details are apparent, though it doesn't address potential downstream effects on related resources.

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

Parameters3/5

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

Schema description coverage is 100% with the single 'id' parameter described as 'Cohort id. Required.' The description's 'by id' phrasing merely echoes the schema without adding new meaning. Baseline of 3 applies because the schema carries the necessary parameter documentation.

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 states a specific verb ('delete'), resource ('saved cohort'), and method ('by id'), and explicitly notes the permanent nature. This clearly distinguishes it from sibling delete tools for other resource types (digest, email_campaign, monitor, scenario).

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?

The description gives no guidance about when to use this tool versus alternative delete tools or other cohort-related tools. There are no prerequisites, exclusions, or conditions stated, leaving the agent to infer usage solely from the name.

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

All RateAPI — live US mortgage, auto, HELOC, personal & deposit rates 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?