Mark

Save Claim

save_claim

Adds or revises a claim on the Claims & sources page. A claim is one fact drafts may state (a certification, price, lead time or spec), backed by a quote that must appear in its source's text. Claims are append-only, so posts that cite a claim keep the wording they were approved against:

Add: text, category, sourceQuote, and either sourceId (list_claims or get_brand_context sources) or source {title, body, url?} to create the source too.
Revise: id of an active claim plus only the fields that change. This retires that claim and creates a new one; the result has the new claim and retiredId. Each call creates a claim. To stop drafts using a claim, call retire_claim. Only active claims reach Mark's drafting and post checks. Related: list_claims, retire_claim, add_source, get_brand_context.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	An active claim's id, to revise it. Omit to add.
`text`	No	The fact, in one sentence.
`source`	No	A new source to create and quote from, instead of sourceId. Nothing is saved if the quote is not in its body.
`category`	No	cert, price, lead_time or spec.
`sourceId`	No	An existing source's id from list_claims.
`sourceQuote`	No	Words copied from the source's text that prove the claim.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes
`claim`	Yes
`appUrl`	Yes
`retiredId`	Yes	The claim that was retired, if any.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 11, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / active

Removed value: -{
-  "const": false,
-  "description": "false, with id only, retires the claim.",
-  "type": "boolean"
-}

changedInput schema / properties / id / description

Previous value: -"An active claim's id, to revise or retire it. Omit to add."New value: +"An active claim's id, to revise it. Omit to add."

changedOutput schema / properties / mode / enum

Previous value: -[
-  "added",
-  "revised",
-  "retired"
-]New value: +[
+  "added",
+  "revised"
+]

AddedOct 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantial context beyond annotations: append-only model so old posts keep approved wording, revision actually retires the old claim and creates a new one returning retiredId, and the quote must appear in the source body or nothing saves. Annotations only say non-readonly/non-destructive; the description explains the real mutation semantics.

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?

Front-loaded with what the tool does, then bullets for Add and Revise, then related tools. Slightly dense with six clauses, but every sentence carries distinct operational meaning.

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?

Given a 6-param tool with nested source object and an output schema (which needn't be restated), the description is complete: it explains both call patterns, the retire-and-recreate side effect, validation of quotes, and downstream effects on drafting and post checks.

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 already 100%, so the baseline is 3, but the description adds the cross-field logic the schema cannot: Add requires text+category+sourceQuote plus either sourceId or source, and Revise needs id plus only changed fields. It explains sourceQuote must be verbatim from the source's text.

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?

States a specific verb (Adds or revises) and resource (a claim), then defines what a claim is and where it lives (Claims & sources page). Clearly distinguishes from siblings like retire_claim and add_source by explaining append-only semantics and the relationship to those tools.

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

Usage Guidelines5/5

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

Explicitly covers both modes (Add vs Revise) with the exact fields each requires, and names retire_claim as the tool for the opposite outcome. States the condition 'Only active claims reach Mark's drafting' so the agent understands the effect.

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

All Mark 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?