jawz

Get World Brief

get_world_brief

Read-only

Read the Jawz World Brief — the weekly Mako-bylined market read published at jawz.ai/brief. Returns the latest edition by default, or a specific one by slug (YYYY-MM-DD). Every claim in a brief traces to a Jawz tool read from its week. Setting list_only:true returns the available editions without their content.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Edition to fetch, YYYY-MM-DD. Omit for the latest.
`list_only`	No	Return only the list of available editions (slug, title, regimeLine, takeaway).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`slug`	No
`title`	No
`byline`	No
`sections`	No
`takeaway`	No
`latest_url`	No
`regimeLine`	No
`canonical_url`	No
`terms_glossary`	No
`available_editions`	No

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds meaningful behavioral context beyond that: the brief is weekly and Mako-bylined, every claim traces to a Jawz tool read from its week, the default is the latest edition, and list_only:true suppresses content and returns only edition metadata.

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?

Two sentences carry all the essential information, with the main purpose front-loaded and supporting detail following naturally. There is no filler, repetition, or ambiguity.

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 two optional parameters, a full input schema, a declared output schema, and annotations indicating a safe read operation, the description supplies everything an agent needs to invoke the tool correctly: what it returns, how to select an edition, and how to request a list-only response.

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?

The input schema already documents slug and list_only with 100% coverage, so the baseline is 3. The description adds the exact slug format (YYYY-MM-DD), that omitting slug returns the latest edition, and that list_only:true returns available editions without content — all useful semantics beyond the raw 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?

The description states a specific verb and resource: 'Read the Jawz World Brief' and clarifies what it returns (latest edition by default, or a specific one by slug). It distinguishes the tool from its siblings by naming the unique publication, the weekly cadence, and the list-only mode.

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?

The description clearly implies when to use the tool — when you need the Jawz World Brief — and explains the two retrieval modes (latest vs. slug, content vs. list-only). However, it does not explicitly name alternative tools or state when not to use it, so the guidance is solid but not fully explicit.

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

All jawz tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools target clearly distinct resources—regime, liquidity, conditions, prices, ETF profiles, data health—and the three history tools are explicitly separated as price, flow, and judgment. The main ambiguity is get_chapter vs run_chapter, which both return chapter framework content and differ only in usage logging, though the descriptions call this out explicitly.

Naming Consistency4/5

The set follows a consistent snake_case verb_noun pattern: get_ for reads, list_ for enumeration, run_ for framework text, and score_ for position drift. The only wrinkle is run_chapter/get_chapter, where 'run' doesn't mean execution but rather 'return framework text and log usage,' making the verb semantics slightly less predictable.

Tool Count4/5

22 tools is on the heavy side but the set is organized into recognizable clusters: macro regime, liquidity/conditions, histories, portfolio drift, ETF/prices, loops/framework, and data health. Each tool appears to earn its place, so the count is slightly high but not bloated.

Completeness4/5

The surface is comprehensive for a read-and-analyze macro/portfolio server: current reads, historical timeseries, data freshness, event calendar, ETF look-through, drift scoring, and loop navigation are all covered. Minor gaps exist—no direct portfolio/position listing tool and non-US central-bank event dates are intentionally not tracked—but these are acknowledged and workable.

Resources

Need Help?