jawz

Get started with Jawz

get_started

Read-only

Orientation for a new Jawz connection, and for questions about what Jawz is, what it covers, or how it is used. Returns where to start (start_here: get_dashboard, the Jawz Dashboard, which gives the state of the world in six readings), a description of the Jawz Loop, example opening prompts, a one-line live market read drawn from the current data layer, a note on the plain-English glossary included in Jawz responses, and a link to the full guide.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`live_now`	No
`start_here`	No
`memory_note`	No
`what_this_is`	No
`audience_note`	No
`first_prompts`	No
`terms_glossary`	No
`how_to_go_deeper`	No
`if_rumo_is_connected`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / start_here

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedSep 6, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
First observedSep 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds one useful behavioral fact beyond that: the output includes a live market read drawn from the current data layer, signaling dynamic content. It says nothing about auth, limits, or freshness caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, which is good, but everything is packed into a single long run-on sentence with a nested parenthetical and six-item return enumeration that is taxing to parse. Content largely earns its place, but the structure could be split for readability.

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?

With zero parameters, safety annotations, and an output schema already present, the description need only establish purpose and usage, which it does. The detailed list of returned fields duplicates the output schema somewhat rather than adding new information.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies a no-argument onboarding call and adds no misleading parameter expectations.

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 (orientation for a new Jawz connection) and enumerates exactly what the tool covers: what Jawz is, what it covers, how it is used. It explicitly distinguishes itself from siblings by naming get_dashboard as the downstream starting point and describing the Jawz Loop as separate content, so an agent can route correctly without opening a schema.

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?

The description gives a clear trigger condition ('for questions about what Jawz is, what it covers, or how it is used') and points at get_dashboard for the state of the world. It does not state explicit when-not-to-use cases or contrast with get_loop/get_chapter, so it stops short of full alternative routing.

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

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?