Skip to main content
Glama

Prexel Markets Pro

Bitcoin Daily Brief

get_daily_brief
Read-onlyIdempotent

Read the saved BTC Daily Brief and its evidence cutoff. Pin report_id and use JSON pointer paths to inspect the exact edition.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_daily_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOmit for the brief overview; pass an empty string for the full report root or a JSON pointer such as /brief/cards. Escape ~ as ~0 and / as ~1.
offsetNoEntry offset for a paged path.
report_idNoExact report_id returned by this tool; required for expansion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds that the brief carries an evidence cutoff and is 'saved' rather than computed live, but says nothing about paging behavior, error cases for a stale report_id, or the cost of expanding large paths.

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?

Two tight sentences with no filler, and the core purpose is front-loaded ahead of the mechanics. It is arguably too compressed for a tool with three interacting parameters, but nothing is wasted.

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?

With annotations and a fully documented schema, most of the burden is carried elsewhere, and the description covers purpose and the expansion mechanic. It leaves unclear what the overview actually returns versus the full report root, which matters because there is no output schema to fall back on.

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 coverage is 100%, so path, offset, and report_id are already documented including the JSON-pointer escaping rules and the omit/empty-string distinction. The description reinforces 'pin report_id' and 'JSON pointer paths' but adds no syntax or edge-case detail beyond the schema, so the baseline 3 applies.

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?

"Read the saved BTC Daily Brief and its evidence cutoff" names a specific verb (read) and resource (saved BTC Daily Brief), so the agent knows it retrieves existing content rather than generating it. It never mentions the sibling get_synthesis, so an agent cannot distinguish the two from this text alone.

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?

"Pin report_id and use JSON pointer paths to inspect the exact edition" gives procedural guidance on how to drill into an edition, which is helpful. It stops short of saying when to call this versus get_synthesis, or when to omit path for the overview versus requesting the full report root.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources