riptide_overviewRiptide health, latest allocation, both paper records, and links.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | ||
| error | No | ||
| schema | Yes | ||
| product | Yes | ||
| available | No | ||
| disclaimer | Yes | ||
| real_orders | Yes | ||
| generated_at | Yes | ||
| execution_mode | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": true,
+ "properties": {
+ "available": {
+ "type": "boolean"
+ },
+ "disclaimer": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "error": {
+ "type": "string"
+ },
+ "execution_mode": {
+ "enum": [
+ "paper_only",
+ "read_only"
+ ]
+ },
+ "generated_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "kind": {
+ "const": "overview",
+ "type": "string"
+ },
+ "product": {
+ "const": "riptide"
+ },
+ "real_orders": {
+ "const": false
+ },
+ "schema": {
+ "const": "riptide.public.v1"
+ }
+ },
+ "required": [
+ "schema",
+ "product",
+ "kind",
+ "generated_at",
+ "execution_mode",
+ "real_orders",
+ "disclaimer"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds content scope but no further behavioral context such as data freshness, aggregation logic, or limitations; this is acceptable but not exceptional.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and front-loads the key content categories, with no filler. However, the telegraphic phrasing ('both paper records, and links') is slightly cryptic and could be clearer as a complete sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, an output schema, and safe annotations, the description is mostly adequate for invoking the tool. It falls short on clarifying how this overview relates to sibling tools and what 'links' refers to, which matters because the tool aggregates content that several siblings also cover.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the input schema fully defines the invocation surface. The description does not need to explain parameter semantics, and the baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description lists content categories ('Riptide health, latest allocation, both paper records, and links') and signals an aggregate overview, but it is a noun phrase with no action verb such as 'provides' or 'returns'. It loosely distinguishes itself from siblings by mentioning allocation and paper records, but does not explicitly name or contrast them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to choose this tool over siblings like riptide_allocation or riptide_paper_record. The description does not mislead, but it leaves the agent to infer usage from the content list alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct information area: allocation, crypto record, event markets, methodology, overview, paper record, and risk evidence. The main potential confusion is that riptide_overview aggregates the latest allocation and both paper records, but the descriptions clarify that it is the summary view while the others provide focused details.
All tool names follow the same riptide_ prefix with a clear lowercase noun-phrase pattern. This is consistent and predictable across the entire set.
Seven tools is well-scoped for a public research and status server. Each tool represents a meaningful, non-redundant surface area, and the count is appropriate for the stated domain.
The set covers the core public surface: overview, allocations, paper records, crypto record, event market availability, methodology, and risk evidence. A minor gap is the lack of historical detail or raw risk event data, but that appears intentional based on the safety boundaries described.