DC Hub

Read Inbox

read_inbox

Read-onlyIdempotent

PARTNER KEY ONLY: notes DC Hub left for the partner agent whose key this session sends, newest first. The first read CONSUMES them (marks read), so a later session sees none; include_read=true re-reads read and unread notes (last 14 days) without marking. Non-partner key: 403. Not a data tool.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Days back (default 14)
`peek`	No	true = do not mark read
`include_read`	No	true = re-read read and unread notes, marks nothing

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier).
`_entity`	No	Payload class (facility\|market\|iso_grid\|queue_results\|deal\|report\|response); branch on it.
`citation`	No	How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
`provenance`	No	Source, method, as_of, verification_counts, license, cite_as; quote it when citing.
`_front_door`	No	First-tool hint: plan_query(intent) returns the ordered plan.
`_return_loop`	No	Next-session delta call (get_changes).
`site_evaluation_handoff`	No	Follow-up calls [{tool, parameters, why}] when the payload carries coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / days

Added value: +{
+  "description": "Days back (default 14)",
+  "maximum": 60,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / include_read

Added value: +{
+  "description": "true = re-read read and unread notes, marks nothing",
+  "type": "boolean"
+}

changedInput schema / properties / peek / description

Previous value: -"true = read without marking the notes read"New value: +"true = do not mark read"

AddedOct 9, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The description says the default call CONSUMES notes by marking them read, i.e. it mutates server-side state, yet annotations declare readOnlyHint=true and destructiveHint=false. That is a direct violation of the read-only contract, and the 'later session sees none' behavior also sits uneasily with idempotentHint=true. The description is the honest party here, but per the contradiction rule it cannot be credited.

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?

Tightly front-loaded: the partner-key restriction and the irreversible consumption warning come before any parameter detail. Every clause carries distinct information (key scope, ordering, consumption, recovery path, error code, tool category) with no filler.

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?

An output schema exists, so return values need not be described, and the description still covers the critical items: key requirement, 403 failure, consumption side effect, and the include_read workaround. It leaves minor gaps, notably the peek parameter and the interaction between days and include_read, so it is nearly but not fully complete.

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%, so the schema already defines days (default 14), peek, and include_read, so the baseline is 3. The description restates include_read's semantics and adds the '(last 14 days)' window for that path, but never mentions the peek parameter or how days interacts with include_read, so it does not meaningfully exceed the schema.

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 and resource (read the DC Hub notes left for the partner agent bound to this session key), plus scope qualifiers 'PARTNER KEY ONLY' and 'newest first'. The closing 'Not a data tool' explicitly separates it from the ~80 sibling intelligence/search tools, so an agent can rule it in or out without opening the schema.

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?

Gives explicit when-to-use conditions (partner key required, non-partner gets 403), the default behavior ('the first read CONSUMES them'), and the alternative invocation pathway (include_read=true re-reads read and unread notes for 14 days without marking). It also states a when-not ('Not a data tool'), which is rare and useful.

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

All DC Hub 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.