MangroveAI

kb_get_signal_quick_reference

Read-onlyIdempotent

Read the Signals Quick Reference guide when the user asks for that guide or its documented entries. This is the document-reading shortcut for kb_get_document slug=10-signals-quick-reference, not an additional validation step. Use view=overview for its outline or view=section with a known anchor for a passage. Content defaults to 6000 characters; offset and next_offset count characters within the selected body. Continue only for requested missing text. Reserve full=True for explicit downloads. For conceptual signal combinations use query_knowledge op=ask. For executable signal names and parameters needed to construct a strategy use the runtime catalogue, not this educational guide.

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": "kb_get_signal_quick_reference"
  }
}

Input Schema

Name	Required	Description	Default
`full`	No	Explicit full content download; cannot combine with offset or max_chars.
`view`	No	Use overview for a brief summary and headings; section for a specific topic; content for document pages.	content
`offset`	No	Pagination offset in the result units documented by the tool; zero starts the first page.
`max_chars`	No	Page size, default 6000, capped at 12000 and the response budget.
`section_anchor`	No	Exact anchor from overview or search, required only for section view.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description is not responsible for safety disclosure. It adds useful behavioral context: default 6000-character content, character-based offset/next_offset pagination within the selected body, full=True reserved for explicit downloads, and continued reading only for requested missing text.

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?

The description is front-loaded with the primary purpose and then efficiently layers routing, pagination, limits, and alternatives. Every sentence carries actionable information with no filler.

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?

For a document-reading shortcut with five optional parameters, no required params, and no output schema, the description supplies complete routing context, pagination semantics, size limits, and sibling alternatives. An agent has everything needed to choose the right view and avoid misusing full=True.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds operational meaning beyond the schema: view=overview yields an outline, view=section requires a known anchor for a passage, full=True is for explicit downloads, and offset/next_offset count characters within the selected body.

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 Signals Quick Reference guide') and explicitly distinguishes this shortcut from kb_get_document slug=10-signals-quick-reference, while also ruling out that it is a validation step. An agent can immediately tell what this tool is and is not.

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?

It gives explicit when-to-use guidance tied to the user asking for the guide or its documented entries, and routes conceptual questions to query_knowledge op=ask and executable signal construction to the runtime catalogue. Clear alternatives and exclusions are provided.

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

All MangroveAI 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.