Mark

List Claims and Sources

list_claims

Read-onlyIdempotent

Lists the Claims & sources page: claims (facts drafts may state, each backed by a quote from a source) and the sources they quote. Each claim has its text, category (cert, price, lead_time, spec), sourceQuote, and its source's id, title and url. Active claims are the ones Mark's drafting and post checks use. A retired claim is kept (retiredAt) because posts that cite it keep its wording; it is never active again. Sources carry their type (note is pasted text; drive_doc syncs from Google Drive), how many claims cite them (claims, active and retired; activeClaims), and hasText (a source without text cannot back a quote). query searches claim text, quotes and source titles, and source titles, links and text, like the page's search. Pass sourceId to see one source's full text (body) and only its claims, before quoting it in save_claim. Does not change anything. Related: save_claim, retire_claim, add_source, update_source, delete_source, get_brand_context.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Case-insensitive text to search for, as on the page.
`status`	No	Which claims to list. Default all, active first.
`category`	No	Only claims in this category.
`sourceId`	No	Only this source and its claims, with the source's full text in body.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`appUrl`	Yes
`claims`	Yes
`counts`	Yes
`sources`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 11, 2026

addedOutput schema / properties / sources / items / properties / claims

Added value: +{
+  "description": "Every claim quoting this source, active and retired.",
+  "type": "number"
+}

addedOutput schema / properties / sources / items / properties / type

Added value: +{
+  "description": "note is pasted text, the only type update_source and delete_source change. drive_doc syncs from Google Drive.",
+  "enum": [
+    "interview",
+    "note",
+    "drive_doc",
+    "website",
+    "intelligence"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / sources / items / required

Previous value: -[
-  "id",
-  "title",
-  "url",
-  "hasText",
-  "activeClaims"
-]New value: +[
+  "id",
+  "type",
+  "title",
+  "url",
+  "hasText",
+  "claims",
+  "activeClaims"
+]

AddedOct 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real domain behavior: retired claims are kept (retiredAt) because citing posts retain wording and a retired claim never reactivates, plus hasText meaning a textless source cannot back a quote. The line 'Does not change anything' only restates readOnlyHint, slightly diluting the added value.

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?

Purpose is front-loaded and the sentences are information-dense, each carrying distinct semantics about claims, sources, and filtering. It runs long relative to a simple list tool, but little is wasted.

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?

An output schema exists, so return values needn't be described, and the description still covers the data model (claim fields, source fields, active/retired lifecycle) and all filtering paths. An agent has everything needed to call and interpret 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 100%, so baseline is 3, but the description goes further: it says query searches claim text, quotes, source titles, links and body text, and that sourceId returns the source's full text in body with only its claims. That clarifies the effect of parameters beyond the terse schema descriptions.

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?

Specific verb (Lists) plus resource (the Claims & sources page), with an immediate clarification of what a claim and a source each are. The definition distinguishes itself from the mutation siblings (save_claim, retire_claim) by explicitly stating it 'Does not change anything.'

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?

Gives concrete routing guidance: pass sourceId to see one source's full text 'before quoting it in save_claim,' and names the Related tools list. It explains what active vs retired claims mean in workflow terms, but stops short of an explicit statement of when to reach for this list versus other listing tools.

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?